-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[CM] Reload not reloading always #10547
Comments
I see a few empty types, this should not be possible with the kibana refactor. |
I've looked at the output, I believe they are fine, I think we correctly handle the inputs, I have added trace in the code, we don't stop the input when we reload the input this mean we still have somehow an harvester linked to the file.
|
Ok after more investigation the above is correct, since the 'reload' method hash the configuration and since the configuration did not change for the inputs we do not stop the inputs, the input stays alive and it should block on the queue when we swap the output and we receive the signal to continue sending events to the queue. |
Now I will take a look more at the logic for swapping outputs. |
This issue should be resolved by the fixes made in #17381. If it reappears in the context of Agent, let's open a new issue. |
I have been testing #10491 and I have saw cases where the reload of configuration did not happen correctly. At first, I thought It was because of an aggressive reload period or fixed for the leaks but this is not the case. I can reproduce the issue all the time with the 6.6 branch.
Steps:
Edit the
api/configurations.go
and make sure that equals always return false, this will force the manager to reload the on each fetch.Use a simple log generator to create an infinite file.
set a 30s or less for the
management.period
option.start filebeat with the following command:
You should see Filebeat read the file and send events to ES on startup, it will periodically fetch and reload the configuration and then it will stop sending events.
The text was updated successfully, but these errors were encountered: