[
https://issues.apache.org/jira/browse/CASSANDRA-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442773#comment-17442773
]
Ekaterina Dimitrova commented on CASSANDRA-17141:
-------------------------------------------------
As per offline discussion, the best option is to maintain both names for some
time.
I will port the backward compatibility for name change from CASSANDRA-15234 to
4.0
> internode_send_buff_size_in_bytes and internode_recv_buff_size_in_bytes from
> cassandra.yaml
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17141
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17141
> Project: Cassandra
> Issue Type: Bug
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> While working on CASSANDRA-17132 I found that in 4.0
> _internode_send_buff_size_in_bytes_ and _internode_recv_buff_size_in_bytes_
> were renamed to
> _internode_socket_send_buffer_size_in_bytes_ and
> _internode_socket_recv_buffer_size_in_bytes_
> but only internally, not in cassandra.yaml. In cassandra.yaml we still have
> the old names.
> Options I see:
> - we decide that there is difference to be acknowledged so we just rename
> and announce the new parameters in NEWS.txt
> - it is confirmed that just a rename was needed. Then do we want to add
> backward compatibility so that anyone who is still looking to start upgrade
> from 3 or 3.11 can directly go smoothly to 4.0.2 without breaking change?
> CC [~benedict] , [~ifesdjeen] and [~aleksey] for your opinion what will be
> the right way to handle this issue.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
