[
https://issues.apache.org/jira/browse/CASSANDRA-16873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16873:
-----------------------------------------
Status: Ready to Commit (was: Review In Progress)
> Tolerate missing DNS entry when completing a host replacement
> -------------------------------------------------------------
>
> Key: CASSANDRA-16873
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16873
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.0.x
>
>
> In one of our deployments, after a host replacement a subset of nodes still
> saw the nodes as JOINING despite the rest of the cluster seeing it as NORMAL
> with a failure to gossip. This was traced to a DNS lookup failure on the
> nodes during an interim state leading to an exception being thrown and gossip
> state never transitioning.
> Rather than implicitly requiring operators to bounce the node by throwing an
> exception, we should instead suppress the exception when checking if a node
> is replacing the same host address and ID if we get an UnknownHostException.
--
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
