-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add parameter to skip ignoring files #4361
Conversation
Why is this DCO failing? I added message required by it at the end of the commit. Can someone help? |
Thanks for your contribution!
The answer is described in the link:
|
In our use-case we have a race condition. We are creating files, then we are setting up privileges. In function 'extend_paths' we can see that if file is not readable once it is ignored, so it happened to us, that some logs were ignored forever. I think that introducing such parameter should be the easiest way to avoid similar problems in the future. Signed-off-by: Artur Laskowski <[email protected]>
173860d
to
78e8cc7
Compare
DCO is now passing |
I will try to fix it later today, I assume this is some problem with new parameter not being properly created. I will take a look |
Signed-off-by: Artur Laskowski <[email protected]>
@ashie PTAL, i made a misspelling before |
Thanks for requesting the new feature!
Does this mean that the following warning log will be no longer shown? fluentd/lib/fluent/plugin/in_tail.rb Lines 306 to 312 in 95438b2
Or mean that the collection of the file will stop forever? |
What I want to achieve is not ignoring any files, it happens that they are unreadable at the beginning, but then gets readable after some time. I am wondering and probably missed that at the beginning, is |
I think that |
@apilaskowski
If the file is not collected after it gets readable, there may be some other issues. |
In our use-case we have a race condition.
We are creating files, then we are setting up privileges. In function 'extend_paths' we can see that if file is not readable once it is ignored, so it happened to us, that some logs were ignored forever.
I think that introducing such parameter should be the easiest way to avoid similar problems in the future.
Which issue(s) this PR fixes:
Fixes #
Rare race condition with updating privileges to files after executing 'in_tail.rb'
What this PR does / why we need it:
Docs Changes:
New parameter in 'in_tail'
Release Note: