-
-
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
[FIXED] only UpdateDelivered
with quorum when clustered
#6139
Conversation
Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
UpdateDelivered
with quorum when clusteredUpdateDelivered
with quorum when clustered
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.
This was by design we would not wait on quorum to deliver messages to consumers.
This one also warrants a discussion IMO prior to a PR.
For what it's worth I think this type of change makes sense. Quorum is what aligns the leader with the followers. If we're making persistent changes to the state of an asset without going through the Raft apply queue, then we've undermined the point of running Raft in the first place and then all bets are completely off when the leader changes. |
Like I said better to discuss on a call / video. |
@derekcollison , I've marked this PR ready for review as well. We've discussed that only the |
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
`store.UpdateDelivered` would always be called, without checking quorum. Which meant that we could get a consumer to be ahead on delivered after switching leader. This change makes `o.updateDelivered` consistent with `o.updateAcks`, which does the same; if clustered propose through RAFT, if not just update delivered directly. Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
store.UpdateDelivered
would always be called, without checking quorum. Which meant that we could get a consumer to be ahead on delivered after switching leader. This change makeso.updateDelivered
consistent witho.updateAcks
, which does the same; if clustered propose through RAFT, if not just update delivered directly.Signed-off-by: Maurice van Veen github@mauricevanveen.com