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

Andres de la Peña commented on CASSANDRA-19047:
-----------------------------------------------

Yes, simply dropping the {{@Deprecated}} annotation and issuing a "manual" 
warning might work too. Rather than making the behaviour of the old guardrail 
depend on the new one, the deprecation warning could be issued if the old 
property is explicitly set in the config (which might be tricky to implement) 
and it has a value different to {{Integer.MAX_VALUE}}, which can be used as a 
disabled value. That way it would be possible to disable both the old and new 
guardrails without getting deprecation guardrails.

> Guardrail for the number of tables is not working
> -------------------------------------------------
>
>                 Key: CASSANDRA-19047
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19047
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Cluster/Schema
>            Reporter: Mohammad Aburadeh
>            Priority: Urgent
>
> Hi, 
> We installed Cassandra 4.1.3 and we got the following warning when creating 
> more than 150 tables: 
> {code:java}
> WARN  [Native-Transport-Requests-6] 2023-11-21 18:35:24,585 
> CreateTableStatement.java:421 - Cluster already contains 161 tables in 6 
> keyspaces. Having a large number of tables will significantly slow down 
> schema dependent cluster operations. {code}
> I tried to disable "table_count_warn_threshold" by setting its value to "-1" 
> but that did not work. 
> Then I tried to set the guardrail for number of tables to "-1" to disable the 
> above but did not work as well. It seems there is no way to disable checking 
> the number of tables. 
> Also,  I tried to set "tables_warn_threshold" to a value less than 
> "tables_count_warn_threshold", it seems Cassandra always uses 
> "tables_count_warn_threshold" when throwing the warning. 
> *Two issues in Cassandra 4.1.3:* 
> 1- There should be a way to disable this feature. Either by setting the 
> guardrail parameter to -1 or setting tables_count_warn_threshold to -1. 
> 2- The guardrail for number of tables should overwrite 
> tables_count_warn_threshold because I always get the following warning when I 
> try to increase the number of tables: 
> {code:java}
> WARN  [main] 2023-11-21 18:26:16,988 YamlConfigurationLoader.java:427 - 
> [keyspace_count_warn_threshold, table_count_warn_threshold] parameters have 
> been deprecated. They have new names and/or value format; For more 
> information, please refer to NEWS.txt {code}



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