-
Notifications
You must be signed in to change notification settings - Fork 757
Jetstream bus pods can't survive the restart #3458
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
Comments
Few additions.
|
Hi, we just encountered the issue for the first time after upgrading I cannot say for sure, but it looks like the issue was triggered through the upgrade of I can confirm that deleting the |
Same here in the same situation. Deleting the pvc and eventbus and recreate them fixes the problem |
We are also encountering this issue |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
We are using jetstream bus in several places. We've noticed that after some time that it working correctly, when one of the pods restarted by the k8s and it is not coming up
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Pod coming up successfuly and syncing with the cluster
Environment (please complete the following information):
Additional context
Logs:
And further logs are combination of pings and this message
till the moment k8s restarting the pod due to failed healthcheck
there are several errors there, probably some are the reasons of the others:
not sure if this is relevant as i saw the same on the healthy pods as well
event bus configuration
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: