-
Notifications
You must be signed in to change notification settings - Fork 4.1k
CASSANDRA-21674 CEP-46: update witness replication validation restrictions #5155
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
Open
bdeggleston
wants to merge
11
commits into
apache:cep-45-mutation-tracking
Choose a base branch
from
bdeggleston:C21674-witness-validation
base: cep-45-mutation-tracking
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
b6aa6c3
Allow any read_repair value on a witness keyspace
bdeggleston d51c225
Reject adding witnesses while a mutation tracking migration is in flight
bdeggleston 71ebf43
Require an opt-in to promote a witness to a full replica
bdeggleston dae5851
Allow secondary indexes on a witness keyspace
bdeggleston 6daa485
Never lead a counter write from a witness replica
bdeggleston 1be6ae1
Cover the Paxos data node selection on a witness keyspace
bdeggleston 26deaff
Correct the transient replication documentation
bdeggleston d4a09f5
remove comments
bdeggleston 3370d88
Move node-configuration dependent keyspace validation to AlterKeyspac…
bdeggleston eaed288
review feedback
bdeggleston ad494fa
Do not select pending nodes as Paxos data node
bdeggleston File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I'm a little concerned about this flag. For this to work correctly, we'll need to uniformly set it on all the nodes of the cluster before running the ALTER command. Otherwise, TCM will fail when following the metadata log and attempting to apply the change. The exception will be thrown if any of the nodes configuration diverges. I guess it can also happen when a node replays the log and the state changes, or if for some reason we set this via JMX, and one of the node restarts. I think in general this approach is a little brittle. So we either need to make sure we document this really well, or we need to find some alternate approach.
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.
yeah it's a little dicey. The problem is that we need some sort of escape hatch to turn off witness replication that doesn't rely on mutation tracking working properly. First of all, we can't correctly promote witnesses without stopping client traffic and running repair at the moment. Once we can though, we still need to get out of bad situations.
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.
yeah, makes absolute sense to have the escape hatch. Just wondering how we should document this to make it visible for operators
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.
pushed a commit that moves config gated validation into the pre-commit validation step