[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719888#comment-17719888
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
Ekaterina pointed out I completely hosed the circle config when I rebased and
my dtest branch wasn't rebased. I've fixed both of those, let's try again:
||Branch||CI||
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1005/workflows/40522429-d127-4625-88ec-c95756012745],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1005/workflows/831b59b2-6414-4e67-a01f-1ec2dc4a54fe]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1006/workflows/458edc48-bff7-41be-82ee-e1cd5aaf604a],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1006/workflows/4b14c842-4962-453d-a7b8-4230e5aa8ddb]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/1004/workflows/855c944b-a0b2-4d04-b635-6a4a6aed2c14],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/1004/workflows/201189e7-637d-429c-90bd-98adf9b3f3fc]|
> 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: 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]
