On Wed, Mar 2, 2016 at 8:10 AM, Peddi, Praveen <pe...@amazon.com> wrote:
> We have few dead nodes in the cluster (Amazon ASG removed those thinking > there is an issue with health). Now we are trying to remove those dead > nodes from the cluster so that other nodes can take over. As soon as I > execute nodetool removenode <ID>, we see lots of HostUnavailableExceptions > both on reads and writes. What I am not able to understand is, these are > deadnodes and don’t even physically exists. Why would removenode command > cause any outage of nodes in Cassandra when we had no errors whatsoever > before removing them. I could not really find a jira ticket for this. > What is your replication factor? Also, 2.0.9 is meaningfully old at this point, consider upgrading ASAP. Also, removing multiple nodes with removenode means your consistency is pretty hosed. Repair ASAP, but there are potential cases where repair won't help. =Rob =Rob
