[ 
https://issues.apache.org/jira/browse/CASSANDRA-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-20657:
-------------------------------------------
    Description: 
All other guardrails can be disabled (with either a blank value or `-1`).

But the following two guardrails do not
tombstone_warn_threshold
tombstone_failure_threshold

For the sake of consistency (and purposes when testing) there should be a way 
to disable these two too.
(Setting them to unrealistically high values, and/or setting warn higher than 
failure, are hacks and not the same thing.)

Part of this ticket can be a few dtests disabling the warn threshold (so to 
avoid erroneous test failures),
e.g. paging_test.py, read_failures_test.py, pushed_notifications_test.py, 
client_request_metrics_test.py

  was:
All other guardrails can be disabled (with either a blank value or `-1`).

But the following two guardrails do not
tombstone_warn_threshold
tombstone_failure_threshold

For the sake of consistency (and purposes when testing) there should be a way 
to disable these two too.

Part of this ticket can be a few dtests disabling the warn threshold (so to 
avoid erroneous test failures),
e.g. paging_test.py, read_failures_test.py, pushed_notifications_test.py, 
client_request_metrics_test.py


> Ability to disable tombstone_warn|failure_threshold guardrails
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-20657
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20657
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Local/Config
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 5.0.x, 5.x
>
>
> All other guardrails can be disabled (with either a blank value or `-1`).
> But the following two guardrails do not
> tombstone_warn_threshold
> tombstone_failure_threshold
> For the sake of consistency (and purposes when testing) there should be a way 
> to disable these two too.
> (Setting them to unrealistically high values, and/or setting warn higher than 
> failure, are hacks and not the same thing.)
> Part of this ticket can be a few dtests disabling the warn threshold (so to 
> avoid erroneous test failures),
> e.g. paging_test.py, read_failures_test.py, pushed_notifications_test.py, 
> client_request_metrics_test.py



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to