-
Notifications
You must be signed in to change notification settings - Fork 189
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
JetStream cluster new consumer leader for '$OCIS > OBJ_service-registry > xxxxx' #7948
Comments
raising to p2 because of critical path for usable nats. |
After investigation, it seems like the cluster is switching the leader on a regular basis. It seems like the output can not be suppressed (unless redirecting it away from |
Please note that it's on a sub-second basis. That doesn't sound healthy for a leader switch From what I understand this is not about the nats jetstream node stream leader change. It can be easily ruled out by having a stream with replica set to 1 (because there is only one node that can be leader, ever) |
Probably :D might have to do with the quorum, https://docs.nats.io/running-a-nats-service/configuration/clustering/jetstream_clustering#the-quorum I am currently experimenting with the scaling to see if the issue persists with a higher number of nodes. |
Ok that does not seem to be the issue. |
Did you look at the NATS source code to see where this log originates? |
haven't digged into the code yet, what I found is that: nats-io/nats-server#4480 |
@wkloucek fixed with move to nats key-value store in 5.0.0-rc2 |
@wkloucek can we close this? |
Didn't have any time yet to look at it / deploy rc.2 |
Ok, when it works, just close it. If there are still issues, let me know. |
Please close it when you feel comfortable. I can always reopen or create another one |
Describe the bug
NATS is logging a lot. Probably triggered by oCIS.
Steps to reproduce
natsjs
service registryExpected behavior
everything is working fine
Actual behavior
everything is working fine from a functional perspective
Only NATS is reporting a lot of messages like:
Setup
Eg. use this example https://github.com/owncloud/ocis-charts/tree/next/deployments/ocis-nats from the
next
branch with oCIS 5.0.0-alpha.6The text was updated successfully, but these errors were encountered: