beobal opened a new pull request, #4613: URL: https://github.com/apache/cassandra/pull/4613
Changing broadcast address has always been supported, but it requires the node to inform the CMS of the change at startup. If a majority of the CMS members attempt to do this concurrently, they have no way to establish the quorum required to make those metadata changes, leading to a deadlocked startup. This is addressed by the combination of 2 patchsets: * CASSANDRA-20736 modifies ClusterMetadata to represent the CMS membership as a set of node ids, rather than addresses. * CASSANDRA-20476 introduces a protocol for nodes starting up to discover the current address for CMS members if they have changed while that node was down. The node can then construct a temporary address lookup which it uses to establish contact with CMS members and update/get the latest agreed ClusterMetadata. When the starting node is itself a CMS member, this lookup enables it to form a consensus group with the other members so that address changes can be durably committed & disseminated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
