Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in_tail: Fix a regression of retrying unaccessible files #3477

Closed
wants to merge 1 commit into from

Conversation

ashie
Copy link
Member

@ashie ashie commented Jul 30, 2021

Which issue(s) this PR fixes:
None.
Follow up of #3378

What this PR does / why we need it:
When a fluentd proccess doesn't have permision to read a file, it should
retry to open it again. But the current implementation doesn't do it due
to a bug introduced at #3378. This pull request intend to rescue EACCESS
on stat(2) but it also rescue it on open(2) wrongly.

Docs Changes:
None

Release Note:
Same with the title.

@ashie
Copy link
Member Author

ashie commented Jul 30, 2021

Tests for it should be added.

@ashie
Copy link
Member Author

ashie commented Jul 30, 2021

In addition, it's better to decrease frequency of retrying: #903

When a fluentd proccess doesn't have permision to read a file, it should
retry to open it again. But the current implementation doesn't do it due
to a bug introduced at #3378. This pull request intend to rescue EACCESS
on stat(2) but it also rescue it on open(2) wrongly.

Signed-off-by: Takuro Ashie <ashie@clear-code.com>
@ashie
Copy link
Member Author

ashie commented Jul 30, 2021

Hmm, it's not a regression, it retries on every tail watcher timer (1 sec).
It's more desired behaviour than before as mentioned in: #903

The only thing we should do is adding warning message for it.
I'll do it in anther pull request.

@ashie ashie closed this Jul 30, 2021
@ashie ashie deleted the in-tail-fix-retrying branch July 30, 2021 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant