[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with dropped mutations


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 to drop mutations are long garbage collection (GC) pauses or large partitions. Do the drops coincide with an increase in requests, a code change, or compaction activity?

On Tue, Jun 26, 2018 at 7:48 AM, Hannu Kröger <hkroger@xxxxxxxxx> wrote:

We have a cluster with somewhat heavy load and we are seeing dropped mutations (variable amount and not all nodes have those).

Are there some clear trigger which cause those? What would be the best pragmatic approach to start debugging those? We have already added more memory which seemed to help somewhat but not completely.


To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxxx

Joshua Galbraith | Senior Software Engineer | New Relic