Skip to content
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

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

MauriceVanVeen
Copy link
Member

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

Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
@MauriceVanVeen MauriceVanVeen requested a review from a team as a code owner November 18, 2024 09:11
@MauriceVanVeen MauriceVanVeen changed the title FIXED: only UpdateDelivered with quorum when clustered [FIXED] only UpdateDelivered with quorum when clustered Nov 18, 2024
Copy link
Member

@neilalexander neilalexander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@derekcollison derekcollison left a 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.

@MauriceVanVeen MauriceVanVeen marked this pull request as draft November 19, 2024 08:38
@neilalexander
Copy link
Member

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.

@derekcollison
Copy link
Member

Like I said better to discuss on a call / video.

@MauriceVanVeen MauriceVanVeen marked this pull request as ready for review November 20, 2024 16:14
@MauriceVanVeen
Copy link
Member Author

@derekcollison , I've marked this PR ready for review as well. We've discussed that only the store delivered state requires quorum so it's consistent on all nodes, and it doesn't block/wait for quorum before sending a message to the client.

@derekcollison derekcollison self-requested a review November 20, 2024 21:06
Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekcollison derekcollison merged commit 32c26d6 into main Nov 20, 2024
5 checks passed
@derekcollison derekcollison deleted the maurice/clustered-update-delivered branch November 20, 2024 21:09
MauriceVanVeen pushed a commit that referenced this pull request Nov 21, 2024
`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>
neilalexander added a commit that referenced this pull request Nov 22, 2024
Includes:

- #6147
- #6150
- #6151
- #6153
- #6154
- #6146
- #6139
- #6152
- #6157
- #6161

Signed-off-by: Neil Twigg <neil@nats.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants