-
Notifications
You must be signed in to change notification settings - Fork 752
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
Unexpectedly extremely many logs during eventbus restart #3497
Comments
It looks like you have fixed it (with adding 10 sec) here: EDIT: Details
|
@ognjen-it . I just saw this issue as well with argo-events
|
facing this issue too on |
Hi @aaron-arellano, I face memory "issues", but that's not worrying... a few hundred megabytes. Do you have some graph/metrics? ![]() @la0bing I think that you don't need to restart to fix it, it will be automatically subscribed to nats jetstream, but logs that sensors have made are problem if you collect those logs.. |
For me the logs never stop, and some sensors showing failed to subscribe to event bus, until I restarted all of them. |
It's so strange. I will focus on solving this problem as soon as my work decreases a bit. But I don't grant I can resolve that :) I faced the issue just like you when I migrated from nats to jetstream, I needed to restart all sensor deployments to catch new secret key for jetstream.
|
Describe the bug
After restarting JetStream (EventBus), Argo Events (Sensor) starts producing an excessive number of errors—over 200,000 errors in a few minutes. This significantly impacts system performance and stability. The issue is consistently reproducible, and logs indicate a flood of reconnection or message processing errors.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Argo Events should gracefully handle JetStream restarts without producing an overwhelming number of errors. It should retry connections in a controlled manner rather than flooding logs and potentially overloading the system.
Screenshots

Log volume of one sensor:
Example of log:
Environment (please complete the following information):
Additional context
Honestly, I wouldn't even have noticed if I didn't have a few dozen sensors and a Loki that had to collect several million logs in those few minutes.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: