You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Isaac Reath (Jira)" <ji...@apache.org> on 2026/05/21 19:56:00 UTC
[jira] [Comment Edited] (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.
[ https://issues.apache.org/jira/browse/CASSANDRA-21024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18082682#comment-18082682 ]
Isaac Reath edited comment on CASSANDRA-21024 at 5/21/26 7:55 PM:
------------------------------------------------------------------
I'll get a fix in for this... good catch.
edit: Stefan is too fast.
was (Author: isaacreath):
I'll get a fix in for this... good catch.
> 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.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-21024
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21024
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
> Reporter: Isaac Reath
> Assignee: Isaac Reath
> Priority: Normal
> Fix For: 6.0-alpha1, 6.0
>
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> [CASSANDRA-17150|https://issues.apache.org/jira/browse/CASSANDRA-17150] introduced disk usage guardrails that stop writes for specific tokens when any replica responsible for those tokens exceeds the configured failure threshold. This mechanism protects individual nodes from running out of disk space but can result in inconsistent write availability when only a subset of replicas or token ranges are affected. This in turn pushes the responsibility onto the application owner to decide how to handle the partial write unavailability.
> We propose adding a new configuration option, data_disk_usage_stop_writes_for_keyspace_on_fail, that extends this behavior to the keyspace level. When enabled, if any node that participates in replication for a keyspace exceeds the disk usage failure threshold, writes to that keyspace will be stopped across all nodes who replicate that keyspace.
> This change provides operators with finer control over guardrail enforcement, allowing them to choose between the current per-token behavior or a stricter, keyspace-wide policy that prioritizes simplicity and operational predictability over partial write availability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org