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 c
Sorry for the late reply. Do you still need assistance with this issue?
If the source of the dropped mutations and high latency are the newer
nodes, that indicates to me that you have an issue with the commitlog
disks. Are the newer nodes identical in hardware configuration to the
pre-existing nod
Hi,
I've extended a cluster by 10% and after that each hour, on some of the nodes
(which changes randomly each time), "dropped mutations cross node" appears on
logs (each time 1 or 2 drops and some times some thousands with cross node
latency from 3000ms to 9ms or 90secon
