Yes correct, for the same node the log message is repeating
On Monday, October 5, 2020, Erick Ramirez
wrote:
> Yes, This log entry is expected during the decommission and happens only
>> once. But in my case I see these messages repeating several 1000 times a
>> day and continuing. Even the
>
> Yes, This log entry is expected during the decommission and happens only
> once. But in my case I see these messages repeating several 1000 times a
> day and continuing. Even the restart of C* process didn't work.
>
Are you saying that the same node is repeatedly reported as going down?
Yes, This log entry is expected during the decommission and happens only
once. But in my case I see these messages repeating several 1000 times a
day and continuing. Even the restart of C* process didn't work.
On Sun, Oct 4, 2020 at 11:49 PM Erick Ramirez
wrote:
> yes correct, I gracefully
Thanks,
I've done a lot of conf changes to fix the problem but nothing worked (last
one was disabling hints) and after a few days problem gone!!
The source of droppedCrossNode was changing every half an hour and it was not
always the new nodes
No difference between new nodes and old ones in
>
> yes correct, I gracefully decommissioned a few nodes from the cluster and
> I see the below log messages for all the decommissioned servers.
>
> INFO [GossipStage:51] 2020-10-05 05:54:10,429 Gossiper.java:1010 -
>> InetAddress /x.x.x.x is now DOWN
>> INFO [GossipStage:51] 2020-10-05
