[
https://issues.apache.org/jira/browse/CASSANDRA-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044098#comment-18044098
]
Stefan Miklosovic commented on CASSANDRA-21057:
-----------------------------------------------
[CASSANDRA-21057-4.1|https://github.com/instaclustr/cassandra/tree/CASSANDRA-21057-4.1]
{noformat}
java8_pre-commit_tests
✓ j8_build 5m 10s
✓ j8_cqlsh_dtests_py3 5m 24s
✓ j8_cqlsh_dtests_py38 5m 58s
✓ j8_cqlsh_dtests_py38_vnode 6m 10s
✓ j8_cqlsh_dtests_py3_vnode 6m 9s
✓ j8_cqlshlib_cython_tests 12m 25s
✓ j8_cqlshlib_tests 11m 27s
✓ j8_dtests_vnode 40m 11s
✓ j8_jvm_dtests 16m 19s
✓ j8_jvm_dtests_repeat 20m 31s
✓ j8_jvm_dtests_vnode 13m 42s
✓ j8_jvm_dtests_vnode_repeat 21m 37s
✓ j8_simulator_dtests 4m 14s
✓ j8_unit_tests 10m 9s
✓ j8_utests_system_keyspace_directory 9m 11s
✓ j11_unit_tests 8m 57s
✓ j11_jvm_dtests_vnode_repeat 20m 18s
✓ j11_jvm_dtests_vnode 16m 48s
✓ j11_jvm_dtests_repeat 21m 9s
✓ j11_jvm_dtests 15m 19s
✓ j11_dtests_vnode 42m 33s
✓ j11_cqlshlib_tests 9m 48s
✓ j11_cqlshlib_cython_tests 11m 44s
✓ j11_cqlsh_dtests_py3_vnode 6m 29s
✓ j11_cqlsh_dtests_py38_vnode 7m 41s
✓ j11_cqlsh_dtests_py38 5m 51s
✓ j11_cqlsh_dtests_py311_vnode 7m 0s
✓ j11_cqlsh_dtests_py311 6m 5s
✓ j11_cqlsh_dtests_py3 6m 45s
✕ j8_cqlsh_dtests_py311 1m 25s
✕ j8_cqlsh_dtests_py311_vnode 1m 16s
✕ j8_dtests 1h 0m 5s
transient_replication_ring_test.TestTransientReplicationRing
test_move_forwards_and_cleanup
replace_address_test.TestReplaceAddress
test_insert_data_during_replace_different_address
✕ j11_dtests 57m 24s
refresh_test.TestRefresh test_refresh_deadlock_startup
{noformat}
[java8_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/6153/workflows/eeef3f62-c101-438b-9cf2-41868567d6]
> 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
> Assignee: Isaac Reath
> Priority: Normal
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
