-
-
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
Limit statsz updates #5470
Limit statsz updates #5470
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.
Looks pretty good, few small comments.
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.
LGTM
This change seems to be causing some tests to flap since the meta layer for jetstream does not have up to date information in order to complete the test. e.g. TestJetStreamSuperClusterOverflowPlacement |
Might need to fix these flappers before merging. We could set the |
|
the race seems unrelated, neither ( |
This test is timing-sensitive and a lower statsz rate limit seems to reduce test flakiness.
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.
LGTM
The race was because your new test Also need to make the tweak to Will take care of it. |
This PR adds a filter to `sendStatsz` that limits statsz updates to the current heartbeat interval (max once per second), adding a `time.Time` field to track the time the last statsz update was sent. This limit should reduce overall `STATSZ` system event load in large clusters while still allowing initial statsz update to quickly reach newly-discovered nodes. Fixes #5469. Signed-off-by: Will Jordan <[email protected]>
This PR adds a filter to
sendStatsz
that limits statsz updates to the current heartbeat interval (max once per second), adding atime.Time
field to track the time the last statsz update was sent. This limit should reduce overallSTATSZ
system event load in large clusters while still allowing initial statsz update to quickly reach newly-discovered nodes.Fixes #5469.
Signed-off-by: Will Jordan [email protected]