[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680245#comment-17680245
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
||Branch||CI||
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-3.11]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/808/workflows/4fb5bf19-19ac-4b32-b31e-45d96e6cf576]
|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-4.0]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/810/workflows/1e042aa7-ac70-494c-9acf-6558200846b6]
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/810/workflows/7bb29f38-3b8f-4bf1-90d9-091cb5607507]
|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-4.1]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/811/workflows/4cb76aa1-d81b-48b3-8741-a2157b648573]
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/811/workflows/27f42dd4-4eb4-4bcc-a849-872bcc8a1e34]
|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-16718-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/809/workflows/b4980d14-b523-4a20-86ba-52d1768f1ff6]
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/809/workflows/4b0f852a-a6df-46b7-ac4b-5792348d877f]
|
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
