cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh McKenzie (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-16873) Tolerate missing DNS entry when completing a host replacement
Date Fri, 27 Aug 2021 19:56:00 GMT


Josh McKenzie updated CASSANDRA-16873:
                Authors: Chris Lohfink, Josh McKenzie  (was: Josh McKenzie)
          Fix Version/s:     (was: 4.0.x)
    Source Control Link:;a=commit;h=f59411f1c985043850154971e9c4066013f355cb
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

I went ahead and did 4.0 and trunk as this is arguably a bug fix as mentioned below. Going
to continue to have that discussion on ML and consider ticket type a bit more deeply in the

Thanks all for the input.

> Tolerate missing DNS entry when completing a host replacement
> -------------------------------------------------------------
>                 Key: CASSANDRA-16873
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Membership
>            Reporter: Josh McKenzie
>            Assignee: Josh McKenzie
>            Priority: Normal
>             Fix For: 4.0.1, 4.1
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message