Unknown reader errors should close reader/tailer to avoid mtail looping on broken fds. #993
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If mtail is tailing a file under a mount, and this mount is gone, mtail reader might block on
This will DoS mtail which won't respond to standard signals and significantly increase its CPU consumption.
Better strategy is to simply close reader/tailer on the broken fd and let the tailer do its job.
Another retryable cases like syscall.ESTALE can be added in future, but for now fail fast seems like a logical approach.