[CASSANDRA-17135] Update docs for CASSANDRA-17132

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 4.0.x, 5.x
• Component/s: Documentation
• Bug Category: Correctness
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Assignee: Erick Ramirez
• Reporter: Ekaterina Dimitrova

Authors

Erick Ramirez

• Created: 10/Nov/21 23:35
• Updated: 08/Jan/24 15:24

Description

Some cleaning of old parameters was done in CASSANDRA-17132.

We need to update the docs respectively after the migration to ASCIIdoc is done:

• Remove any references to otc_backlog_expiration_interval_ms, otc_coalescing_strategy, otc_coalescing_window_us_default, otc_coalescing_window_us, otc_coalescing_enough_coalesced_messages, internode_application_timeout_in_ms.  Inform the users about deprecation of otc_backlog_expiration_interval_ms, otc_coalescing_strategy, otc_coalescing_window_us_default, otc_coalescing_window_us, otc_coalescing_enough_coalesced_messages.
  internode_application_timeout_in_ms - this one never existed internally so I am not sure whether we need to add it now to Config.java... It was only a commented property in cassandra.yaml that never got into the release
• The names of internode_send_buff_size_in_bytes and internode_recv_buff_size_in_bytes to be changed to 

internode_socket_send_buffer_size_in_bytes and internode_socket_recv_buffer_size_in_bytes everywhere in the docs

Issue Links

• is related to: CASSANDRA-15234 Standardise config and JVM parameters
• is related to: CASSANDRA-17132 Fix startup issue with internode_application_timeout_in_ms