[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408402#comment-17408402
]
Brandon Williams edited comment on CASSANDRA-16718 at 9/7/21, 8:30 PM:
-----------------------------------------------------------------------
-This has been broken since CASSANDRA-10134, though I'm not sure how yet-.
What is strange to me is that this issue persists even if both nodes are
restarted, so something is being persisted incorrectly here.
was (Author: brandon.williams):
This has been broken since CASSANDRA-10134, though I'm not sure how yet. What
is strange to me is that this issue persists even if both nodes are restarted,
so something is being persisted incorrectly here. I'll have to look more
tomorrow.
> 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
>
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
