You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used AWS servers, using servers in different countries. There were servers in four countries in total, three servers in each country, and a total of 12 servers to build the nats cluster.The number of copies is 3, the message volume is not large, but the bandwidth usage is abnormal.
Expected behavior
There are more than thirty streams in total, and there are about twenty consumers every month. If twelve clusters are used as a cluster, the upstream and downstream bandwidth should not be so high.
Server and client version
Using the latest nats-server version
Host environment
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered:
Is the topology 12 servers clustered together with routes over different regions? Do you see any readloop processing errors or Slow Consumer errors in the logs? Have you tried modifying the max_outstanding_catchup setting from JetStream to something lower max_outstanding_catchup=32mb?
wallyqs
changed the title
Abnormal bandwidth usage of nats cluster service
Abnormal bandwidth usage of nats cluster service [v2.10.22, v2.10.23]
Dec 11, 2024
wallyqs
changed the title
Abnormal bandwidth usage of nats cluster service [v2.10.22, v2.10.23]
Abnormal bandwidth usage of nats cluster service [v2.10.22 || v2.10.23]
Dec 11, 2024
Observed behavior
I used AWS servers, using servers in different countries. There were servers in four countries in total, three servers in each country, and a total of 12 servers to build the nats cluster.The number of copies is 3, the message volume is not large, but the bandwidth usage is abnormal.
Expected behavior
There are more than thirty streams in total, and there are about twenty consumers every month. If twelve clusters are used as a cluster, the upstream and downstream bandwidth should not be so high.
Server and client version
Using the latest nats-server version
Host environment
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: