[
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413402#comment-17413402
]
Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------
[Here|https://github.com/driftx/cassandra/tree/CASSANDRA-16718] is a 3.11
branch that passes a slightly more thorough [dtest that reads at
ALL|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-16718] in a [CI
run|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1108/pipeline].
This works by removing the _use_ of persistence in OutboundTcpConnectionPool,
but still persists the IP for later usage, and ReconnectingSnitchHelper
_removes_ the INTERNAL_IP state upon the node being marked down so that changes
can be learned in the next connection.
I'll have to come up with something similar for 4.0 and trunk, since they don't
have OTCP after the messaging service refactoring.
> 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]
