[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716848#comment-17716848
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
Rebased:
||Branch||CI||
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/987/workflows/10f7377e-82a4-4e3c-a1ef-9a4434cf2dec],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/987/workflows/62eee3b3-b51b-4f86-bdaf-77e102787b47]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/985/workflows/5341072c-542e-4f0a-af90-98624e59cc07],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/985/workflows/5e3a1e1f-7004-48fc-b0c6-faff7ef95914]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/986/workflows/9ab17625-3937-4daf-9c73-ffa77cc0f703],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/986/workflows/1d17e818-b3b2-4732-bb11-75f77d6de8d3]|
> 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, 5.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]