CASSANDRA-21024: Add configuration to disk usage guardrails to stop writes across all replicas of a keyspace when any node replicating that keyspace exceeds the disk usage failure threshold. #4547
Conversation
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
…rites across all replicas of a keyspace when any node replicating that keyspace exceeds the disk usage failure threshold. This commit adds a new configuration, data_disk_usage_stop_writes_for_keyspace_on_fail, which ensures that if any node which replicates a given keyspace is full, all writes to that keyspace are blocked.
isaacreath
force-pushed
the
CASSANDRA-21024-trunk
branch
from
736cf52 to
5b1845c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This patch adds a new configuration,
data_disk_usage_stop_writes_for_keyspace_on_fail, which ensures that if any node which replicates a given keyspace is full, all writes to that keyspace are blocked. The goal of this configuration is to provide simpler semantics to users of this guardrail, instead of having to deal with managing write failures to a subset of replicas in the cluster.