[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416192#comment-17416192
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
Hmm, no. I left the [call in reconnect that updates
it|https://github.com/driftx/cassandra/commit/f2b7b335a89c64eb478424eb6a9a027e59995c4a#diff-3fe65944fc6b986688040b3a9400cd5a0bd798cca29e0f3b399db5ece33dc1f1L108]
intentionally so CASSANDRA-8084 would continue to work, I only removed an
earlier call to retrieve it. How did you observe this?
This raises a greater question though, perhaps we should remove the persistence
altogether and rework CASSANDRA-8084's bits to work like this too. I'll wait
for reviewer feedback before pulling that trigger though.
> 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: [email protected]
For additional commands, e-mail: [email protected]
