[jira] [Commented] (CASSANDRA-21057) Disk usage guardrail cannot be disabled when failure threshold is reached

["Stefan Miklosovic (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042414#comment-18042414 ] 

Stefan Miklosovic commented on CASSANDRA-21057:
-----------------------------------------------

hey nice catch, if you or [~isaacreath] prepares a patch I can review.

> Disk usage guardrail cannot be disabled when failure threshold is reached
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21057
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21057
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Feature/Guardrails
>            Reporter: Paulo Motta
>            Priority: Normal
>
> When the max allowed disk usage is reached, the node stop accepting writes. In case the operator wants to disable the guardrail so the node start accepting writes again, it is not able to do so by attempting to unset the warning and failure thresholds to null at runtime:
> {code}
> nodetool-all setguardrailsconfig data_disk_usage_percentage_threshold null null
> {code}
> The reason for this is because the node does not stop advertising it's {{FULL}} via gossip. We should set the state to {{SPACIOUS}} when the guardrail is disabled at runtime.
> A workaround for this is to set the data_disk_usage_max_disk_size to a very high value:
> {code}
> nodetool-all setguardrailsconfig data_disk_usage_max_disk_size 10000GiB # set to a very large value
> {code}



--
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