cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-16718) Changing listen_address with prefer_local may lead to issues
Date Wed, 01 Sep 2021 14:27:00 GMT

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

Brandon Williams commented on CASSANDRA-16718:
----------------------------------------------

Adjusting fixvers as this passes on 3.0, but not 3.11 or 4.0.

> 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.0.x, 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message