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
[IMPROVED] Raft layer improvements #4020
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.
LGTM 💯
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!
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!
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!
…g the monitor Signed-off-by: Derek Collison <derek@nats.io>
…e sure they are only processed if explicitly new Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
Signed-off-by: Derek Collison <derek@nats.io>
967499a
to
7d3ec51
Compare
Two changes here.
Revert of a change regarding handling of leadership transfer entries that caused instability in some tests and a bad upgrade experience.
Make sure if we detect that a stream or a consumer is already running the monitoring routines that we do not stop the underlying raft group since it will be being used in the monitor routine and would stall that asset.
Signed-off-by: Derek Collison derek@nats.io