[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690357#comment-17690357
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
We can remove testEc2MRSnitch since that is removed in 4.0 and later anyway...
but the real issue is 3.11 doesn't work correctly. Either
test_prefer_local_reconnect_on_listen_address or
test_prefer_local_reconnect_on_restart fails depending on which approach is
attempted.
Given this, and that the message service was
[rewritten|https://issues.apache.org/jira/browse/CASSANDRA-15066] for 4.0, and
with 4.2/5.0 releasing in the coming months which will EOL it, I think we
should just quit targeting 3.11.
Then we can rebase and run CI and we should be ready.
> Changing listen_address with prefer_local may lead to issues
> ------------------------------------------------------------
>
> Key: CASSANDRA-16718
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16718
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Jan Karlsson
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x, 4.x
>
>
> Many container based solution function by assigning new listen_addresses when
> nodes are stopped. Changing the listen_address is usually as simple as
> turning off the node and changing the yaml file.
> However, if prefer_local is enabled, I observed that nodes were unable to
> join the cluster and fail with 'Unable to gossip with any seeds'.
> Trace shows that the changing node will try to communicate with the existing
> node but the response is never received. I assume it is because the existing
> node attempts to communicate with the local address during the shadow round.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
