-
Notifications
You must be signed in to change notification settings - Fork 247
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
Hot reload issues #1249
Comments
how does fluent-operator know when your operations are done? in my opinion, you can control the create/delete orders in your CI system and this problem will be resolved. |
how exactly you're suggesting to control it? |
@cw-Guo we use gitops to deploy and when we deploy a bigger application, many fluent-operator CRs gets created that seems to trigger many reload on fluent-bit pods. This causes troubles for us as fluent-bit starts hanging from time to time (#1332). It seems, fluent-bit has some issues with hot reload: fluent/fluent-bit#9354 While, these are most probably fluent-bit bugs, maybe being a bit more "kind" with the reload requests could help. How about a solution that instead of immediately reload on every CR change, fluent-operator would "collect" the changes for some definable period (like 1 minute) and call a single reload only once if any change has happened during this period. ping @markusthoemmes |
I'm not really active in this project right now, but I did solve this internally eventually. Essentially, I've created a script that gets the current reloads ( |
Describe the issue
We've got CI which deploys filters, parsers and outputs into several namespaces. It works like this: before deployment it deletes everything in namespace.
Started from version 2.7.0 we've got following errors:
Looks like it is reloading on every object deletion. And when parsers are deleted before filters, it stucks and crashes.
Then restarts normally.
To Reproduce
Expected behavior
Your Environment
How did you install fluent operator?
helm
Additional context
No response
The text was updated successfully, but these errors were encountered: