-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Nats[2.10.21] inaccessible consumers in nats with 3 node cluster, slowness in publishing messages, high CPU and memory, idle consumers #6296
Comments
What does |
Output of
|
With zero votes (which is good), something else must be going on with your setup to cause the system to not elect a meta-leader. |
@derekcollison is there a list of check points which I can run to identify root cause. Following things I have validated:
|
It may be that you are running out of CPU. Try giving them more CPU, say 4 or 8, and possibly bumping memory as well, 8GB. |
Few more observations:
In my past experience with this issue, restart has resolved the issue temporarily. Allocating more cpu/memory may solve the issue for while. Thanks |
I would also upgrade to the latest server version and make sure you still see any issues - 2.10.24. |
I would recommend at least 4 vcpus to avoid long unexpected pauses, with 2vcpus you would often seen
|
Observed behavior
Experiencing extreme slowness in nats 3 nodes cluster.
Following are observations:
Output of
nats consumer report stream_name
:Output of
nats server ls
from all 3 nodes:Output of
nats server report jetstream
:Output of
nats stream subjects
:Sudden increase in Cluster NTT
Sudden increase in Poll Time
CPU usage:
Memory usage:
Resource and limit:
Env variables:
Nats configuration:
Expected behavior
Under load, nats should deliver messages to consumer without any slowness
Server and client version
Nats Server Version 2.10.21
Nats Client Version 1.37.0 (Golang Application)
Host environment
Steps to reproduce
No steps to reproduce. Happening randomly. Happened 3 times in last 3 months
The text was updated successfully, but these errors were encountered: