You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ling Mao (Jira)" <ji...@apache.org> on 2025/09/05 13:15:00 UTC
[jira] [Updated] (CASSANDRA-20892) Don't allow JMX operations for denylist when denylist is disabled
[ https://issues.apache.org/jira/browse/CASSANDRA-20892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ling Mao updated CASSANDRA-20892:
---------------------------------
Description:
While following the documentation ([2]), I executed the following commands
{code:java}
bean org.apache.cassandra.db:type=StorageProxy
run denylistKey foo buz 3
true
run loadPartitionDenylist
true
run isKeyDenylisted foo buz 3
false
{code}
but encountered some confusing behavior:
The function isKeyDenylisted always returned false, which was unexpected.
However, I observed from the logs that loadPartitionDenylist executed successfully:
Loaded partition denylist cache in 24ms
Additionally, running the query SELECT * FROM foo.buz WHERE key=3; did not throw an exception as anticipated.
After further investigation, I discovered that the feature needs to be explicitly enabled by setting partition_denylist_enabled: true in the cassandra.yaml file. Unfortunately, this requirement is not mentioned in the documentation ([1], [2]).
Reference:
[1] https://cassandra.apache.org/doc/latest/cassandra/managing/operating/denylisting_partitions.html
[2] https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Denylisting-Partitions.html
> Don't allow JMX operations for denylist when denylist is disabled
> -----------------------------------------------------------------
>
> Key: CASSANDRA-20892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20892
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Observability/JMX
> Reporter: Ling Mao
> Priority: Normal
>
> While following the documentation ([2]), I executed the following commands
>
> {code:java}
> bean org.apache.cassandra.db:type=StorageProxy
> run denylistKey foo buz 3
> true
> run loadPartitionDenylist
> true
> run isKeyDenylisted foo buz 3
> false
> {code}
>
> but encountered some confusing behavior:
> The function isKeyDenylisted always returned false, which was unexpected.
> However, I observed from the logs that loadPartitionDenylist executed successfully:
> Loaded partition denylist cache in 24ms
> Additionally, running the query SELECT * FROM foo.buz WHERE key=3; did not throw an exception as anticipated.
> After further investigation, I discovered that the feature needs to be explicitly enabled by setting partition_denylist_enabled: true in the cassandra.yaml file. Unfortunately, this requirement is not mentioned in the documentation ([1], [2]).
> Reference:
> [1] https://cassandra.apache.org/doc/latest/cassandra/managing/operating/denylisting_partitions.html
> [2] https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Denylisting-Partitions.html
--
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