Need to review java gc, system , network, disk, memory, node, and table
statistics. A lot can be discerned from visually examining the charts. Eg. if
the nodes with the most local reads is failing or is it the one with the most
writes or is it completely unrelated.
Since it’s a distributed syst
Thanks for your prompt replies. No the same node is not bouncing over. When
you say it is about to tip over: What can we do to stop that ?
Also about that error : you guys are correct: it is a warning and might
not be contributing to the node bounce issue and it can be removed by
changing batch_s
Do the same nodes reboot or is it arbitrary? I’m wondering if it’s an isolated
incident related to dat / traffic skew or could happen on any coordinator
Rahul
On Jul 26, 2018, 12:31 AM -0400, Jeff Jirsa , wrote:
> It’s a warning, but probably not causing you problems
>
> A 20kB batch is a hint th
It’s a warning, but probably not causing you problems
A 20kB batch is a hint that your batches are larger than Cassandra expects, but
the 5k limit for that logger was somewhat arbitrary, and I would be shocked if
20kB batches were a problem unless you were already close to tipping your
cluster
