cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anubhav Kale (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10580) Add latency metrics for dropped messages
Date Wed, 16 Dec 2015 17:40:46 GMT


Anubhav Kale commented on CASSANDRA-10580:

My HEAD is indeed pointing to different location: f1c3df0e848638735c790b4817adf6411a52a064.
I pulled down 2.2. via below and then made changes.

git clone cassandra-2.2

I will dig some more on why this did not work correctly.

> Add latency metrics for dropped messages
> ----------------------------------------
>                 Key: CASSANDRA-10580
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Coordination, Observability
>         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, 2.2-All-Comments.patch,
CASSANDRA-10580-Head.patch, Trunk-All-Comments.patch, Trunk.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