cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anubhav Kale (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-10580) On dropped mutations, more details should be logged.
Date Mon, 14 Dec 2015 22:12:46 GMT


Anubhav Kale edited comment on CASSANDRA-10580 at 12/14/15 10:12 PM:

Thanks for the pointers. Please take a look at the latest patch. I have tested it via Visual
VM and the new metrics work well. 

It is interesting that I could not find any documentation that Metrics return results (.getSnapshot.GetMean())
in nanoseconds therefore callers must convert themselves. Noting this here so other Devs can
save some time on this.

I'll file a separate JIRA for doing the same change on a per ks/cf basis. 

Let me know this makes sense, or more changes are needed. 

was (Author: anubhavk):
Patch for exposing this data as JMX metrics

> On dropped mutations, more details should be logged.
> ----------------------------------------------------
>                 Key: CASSANDRA-10580
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Coordination
>         Environment: Production
>            Reporter: Anubhav Kale
>            Assignee: Anubhav Kale
>            Priority: Minor
>             Fix For: 3.2, 2.2.x
>         Attachments: 0001-Metrics.patch, 10580-Metrics.patch, 10580.patch, CASSANDRA-10580-Head.patch,
> In our production cluster, we are seeing a large number of dropped mutations. At a minimum,
we should print the time the thread took to get scheduled thereby dropping the mutation (We
should also print the Message / Mutation so it helps in figuring out which column family was
affected). This will help find the right tuning parameter for write_timeout_in_ms. 
> The change is small and is in and I will submit
a patch shortly.

This message was sent by Atlassian JIRA

View raw message