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) +
stora
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
Hello,
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 seem
For while only in local machine, but we will do it in test environment.
Thanks.
2018-06-25 16:15 GMT+08:00 dinesh.jo...@yahoo.com.INVALID <
dinesh.jo...@yahoo.com.invalid>:
> If you're working in a different keyspace, I don't anticipate any issues.
> Have you attempted one in a test cluster? :)
>
