[ 
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411468#comment-17411468
 ] 

Brandon Williams edited comment on CASSANDRA-16718 at 9/7/21, 8:38 PM:
-----------------------------------------------------------------------

Actually, CASSANDRA-10134 didn't break this, but it fixed the server's behavior 
such that the test was deterministic after it; before we will mark the node up, 
but then fail to connect to the old IP forever and eventually mark the node 
back down due to lack of communication, tricking the test into thinking it 
passed. :(  I will keep digging, but I suspect the solution is likely the same: 
don't persist and use preferred_ip, only the gossip state that is present.


was (Author: brandon.williams):
Actually, CASSANDRA-10134 didn't break this, but it fixed the server's behavior 
such that the test was deterministic after it; before we will mark the node up, 
but then fail to connect to the old IP forever and eventually mark the node 
back down due to lack of communication, tricking the test into thinking it 
passed. :(  I will keep digging.

> 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

Reply via email to