Dropped mutations are load shedding - somethings not happy.
Are you seeing GC pauses?
What heap size and version?
What memtable settings ?
--
Jeff Jirsa
> On Jul 2, 2018, at 12:48 AM, Hannu Kröger wrote:
>
> Yes, there are timeouts sometimes but more on the read side. And yes, there
>
Yes, there are timeouts sometimes but more on the read side. And yes, there are
certain data modeling problems which will be soon addressed but we need to keep
things steady before we get there.
I guess many write timeouts go unnoticed due to consistency level != ALL.
Network looks to be
Are you also seeing time-outs on certain Cassandra operations?? If yes, you may
have to tweak *request_timeout parameter in order to get rid of dropped
mutation messages if application data model is not upto mark!
You can also check if network isn't dropping packets (ifconfig -a tool) +
Hannu,
Dropped mutations are often a sign of load-shedding due to an overloaded
node or cluster. Are you seeing resource saturation like high CPU usage
(because the write path is usually CPU-bound) on any of the nodes in your
cluster?
Some potential contributing factors that might be causing you
