|
| 1 | +CCM (Cassandra Cluster Manager) |
| 2 | +CASSANDRA-17379 README |
| 3 | +==================================================== |
| 4 | + |
| 5 | + |
| 6 | +---- |
| 7 | + |
| 8 | + |
| 9 | + |
| 10 | +WARNING - CCM configuration changes using updateconf does not happen according to CASSANDRA-17379 |
| 11 | +------------------------------------------------------------------------------------------------- |
| 12 | + |
| 13 | +After CASSANDRA-15234, to support the Python upgrade tests CCM updateconf is replacing |
| 14 | +new key name and value in case the old key name and value is provided. |
| 15 | +For example, if you add to config `permissions_validity_in_ms`, it will replace |
| 16 | +`permissions_validity` in default cassandra.yaml |
| 17 | +This was needed to ensure correct overloading as CCM cassandra.yaml has keys |
| 18 | +sorted lexicographically. CASSANDRA-17379 was opened to improve the user experience |
| 19 | +and deprecate the overloading of parameters in cassandra.yaml. In CASSANDRA 4.1+, by default, |
| 20 | +we refuse starting Cassandra with a config containing both old and new config keys for the |
| 21 | +same parameter. Start Cassandra with `-Dcassandra.allow_new_old_config_keys=true` to override. |
| 22 | +For historical reasons duplicate config keys in cassandra.yaml are allowed by default, start |
| 23 | +Cassandra with `-Dcassandra.allow_duplicate_config_keys=false` to disallow this. Please note |
| 24 | +that key_cache_save_period, row_cache_save_period, counter_cache_save_period will be affected |
| 25 | +only by `-Dcassandra.allow_duplicate_config_keys`. Ticket CASSANDRA-17949 was opened to decide |
| 26 | +the future of CCM updateconf post CASSANDRA-17379, until then - bear in mind that old replace |
| 27 | +new parameters' in cassandra.yaml when using updateconf even if |
| 28 | +`-Dcassandra.allow_new_old_config_keys=false` is set by default. |
| 29 | + |
| 30 | +TLDR Do not exercise overloading of parameters in CCM if possible. Also, the mentioned changes |
| 31 | +are done only in master branch. Probably the best way to handle cassandra 4.1 in CCM at this |
| 32 | +point is to set `-Dcassandra.allow_new_old_config_keys=false` and |
| 33 | +`-Dcassandra.allow_duplicate_config_keys=false` |
| 34 | +to prohibit any kind of overloading when using CCM master and CCM released versions |
0 commit comments