-
Notifications
You must be signed in to change notification settings - Fork 95
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
rel: prep 2.7 release #1255
rel: prep 2.7 release #1255
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recommended copyedit
Nodes calculate a cluster stress level as a weighted average (with nodes that are more stressed getting more weight). | ||
If an individual node is stressed, it can enter stress relief individually. | ||
This may happen, for example, when a single giant trace is concentrated on one node. | ||
If the cluster as a whole is being stressed by a general burst in traffic, the entire cluster should now enter or leave stress relief at approximately the same time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean that you could expect to see a rise in cross-node network traffic, or do we expect it to be marginal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might see the impact of pubsub traffic to and from redis, but it's pretty small; we mostly only publish new values when they're different.
Co-authored-by: Phillip Carter <pcarter@fastmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me wrt docs! 🎉 Thank you @kentquirk!
Prep 2.7 release