0

I need some advice I upgraded my cassandra cluster which had 7 nodes on Ubuntu 22.04 from 4.0.5 to 4.1.7 How I did it:

I continued it for each nodes. And after that I got the warning:

WARN 08:50:08,758 [dynamic_snitch_reset_interval_in_ms, tracetype_query_ttl, request_timeout_in_ms, row_cache_size_in_mb, counter_write_request_timeout_in_ms, column_index_size_in_kb, trickle_fsync_interval_in_kb, cas_contention_timeout_in_ms, key_cache_size_in_mb, range_request_timeout_in_ms, enable_transient_replication, dynamic_snitch_update_interval_in_ms, column_index_cache_size_in_kb, write_request_timeout_in_ms, index_summary_resize_interval_in_minutes, permissions_validity_in_ms, max_hint_window_in_ms, enable_user_defined_functions, enable_sasi_indexes, read_request_timeout_in_ms, enable_drop_compact_storage, enable_legacy_ssl_storage_port, credentials_validity_in_ms, batch_size_warn_threshold_in_kb, index_summary_capacity_in_mb, commitlog_sync_period_in_ms, batchlog_replay_throttle_in_kb, windows_timer_interval, enable_scripted_user_defined_functions, commitlog_segment_size_in_mb, sstable_preemptive_open_interval_in_mb, tracetype_repair_ttl, roles_validity_in_ms, enable_materialized_views, prepared_statements_cache_size_mb, hinted_handoff_throttle_in_kb, compaction_large_partition_warning_threshold_mb, truncate_request_timeout_in_ms, slow_query_log_timeout_in_ms, hints_flush_period_in_ms, counter_cache_size_in_mb, max_hints_file_size_in_mb, compaction_throughput_mb_per_sec, batch_size_fail_threshold_in_kb] parameters have been deprecated. They have new names and/or value format; For more information, please refer to NEWS.txt

As I can see in docs https://cassandra.apache.org/doc/4.1/cassandra/configuration/cass_yaml_file.html I should comment this parameters in cassandra.yaml:

  • dynamic_snitch_reset_interval_in_ms
  • tracetype_query_ttl
  • request_timeout_in_ms
  • row_cache_size_in_mb
  • counter_write_request_timeout_in_ms
  • column_index_size_in_kb
  • trickle_fsync_interval_in_kb
  • cas_contention_timeout_in_ms
  • key_cache_size_in_mb
  • range_request_timeout_in_ms
  • enable_transient_replication
  • dynamic_snitch_update_interval_in_ms
  • column_index_cache_size_in_kb
  • write_request_timeout_in_ms
  • index_summary_resize_interval_in_minutes
  • permissions_validity_in_ms
  • max_hint_window_in_ms
  • enable_user_defined_functions
  • enable_sasi_indexes
  • read_request_timeout_in_ms
  • enable_drop_compact_storage
  • enable_legacy_ssl_storage_port
  • credentials_validity_in_ms
  • batch_size_warn_threshold_in_kb
  • index_summary_capacity_in_mb
  • commitlog_sync_period_in_ms
  • batchlog_replay_throttle_in_kb
  • windows_timer_interval
  • enable_scripted_user_defined_functions
  • commitlog_segment_size_in_mb
  • tracetype_repair_ttl
  • roles_validity_in_ms
  • enable_materialized_views
  • prepared_statements_cache_size_mb
  • hinted_handoff_throttle_in_kb
  • compaction_large_partition_warning_threshold_mb
  • truncate_request_timeout_in_ms
  • slow_query_log_timeout_in_ms
  • hints_flush_period_in_ms
  • counter_cache_size_in_mb
  • max_hints_file_size_in_mb
  • compaction_throughput_mb_per_sec
  • batch_size_fail_threshold_in_kb

And sstable_preemptive_open_interval_in_mb chang to sstable_preemptive_open_interval

Is It right?

Improve this question

1 Answer 1

Reset to default
1

You are correct. A lot of the parameters have been renamed in Cassandra 4.1 in an effort to standardise the configuration properties and JVM options in future releases (CASSANDRA-15234).

The old property names were deprecated but not removed so the message at startup is logged at WARN level (not ERROR) since they will continue to work at least until C* 5.x but there are some things you need to be aware of when upgrading a cluster. Here is an extract of the announcement in NEWS.txt:

- There is a new cassandra.yaml version 2. Units suffixes should be provided for all rates(B/s|KiB/s|MiB/s), memory (B|KiB|MiB|GiB) and duration(d|h|m|s|ms|us|µs|ns) parameters. List of changed parameters and details to consider during configuration setup can be found at https://cassandra.apache.org/doc/latest/cassandra/new/configuration.html. (CASSANDRA-15234) Backward compatibility with the old cassandra.yaml file will be in place until at least the next major version. By default we refuse starting Cassandra with a config containing both old and new config keys for the same parameter. Start Cassandra with -Dcassandra.allow_new_old_config_keys=true to override. For historical reasons duplicate config keys in cassandra.yaml are allowed by default, start Cassandra with -Dcassandra.allow_duplicate_config_keys=false to disallow this.

Additionally, Ekaterina Dimitrova wrote a blog post in July 2022 announcing the change in Apache Cassandra 4.1: Configuration Standardization.

For a list of the renamed properties, see Liberating cassandra.yaml Parameters' Names from Their Units on the official Apache Cassandra website. Cheers!

Improve this answer
4
  • Thank you for answer! Commented Jan 28 at 8:39
  • You're welcome, @КоляКурик! Please see What to do when someone answers if you're happy with my answer. Cheers! Commented Jan 28 at 11:44
  • Thank you again ) Commented Jan 28 at 14:01
  • Happy to help! 👍 Commented Jan 28 at 22:15

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.