Another workaround that i used for UNREACHABLE nodes problem, is to restart the
whole cluster and it would be fixed, but i don't know if it cause any problem
or not
Sent using https://www.zoho.com/mail/
On Fri, 18 Sep 2020 01:19:35 +0430 Paulo Motta
wrote
Oh, if you're adding t
Oh, if you're adding the same hosts to another cluster then the old cluster
might try to communicate to the decommissioned nodes if you do that before
the 3 day grace period. The cluster name not matching is a good protection,
otherwise the two clusters will connect to each other and mayhem will
en
Thanks Paulo,
We have to decommission multiple nodes from the cluster and move those
nodes to other clusters.
So if we have to wait for 3 days for every node then it is going to take a
lot of time.
If i am trying to add the decommissioned node to the other cluster it is
giving me an error that cl
After decommissioning the node remains in gossip for a period of 3 days (if
I recall correctly) and it will show up on describecluster during that
period, so this is expected behavior. This allows other nodes that
eventually were down when the node decommissioned to learn that this node
left the cl
We are on 3.11.5 opensource cassandra
On Thu, Sep 17, 2020 at 10:25 AM Krish Donald wrote:
> Hi,
>
> We decommissioned a node from the cluster.
> On decommissioned node it said in system.log that node has been
> decommissioned .
> But after couple of minutes only , on rest of the nodes the node
Hi,
We decommissioned a node from the cluster.
On decommissioned node it said in system.log that node has been
decommissioned .
But after couple of minutes only , on rest of the nodes the node is showing
UNREACHABLE when we issue nodetool describecluster .
nodetool status is not showing the node
