cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10580) On dropped mutations, more details should be logged.
Date Wed, 09 Dec 2015 23:08:10 GMT


Paulo Motta commented on CASSANDRA-10580:

I mean in this statement:
            	logger.warn("LocalMutationRunnable thread ran after {} ms, allowed time was {}
ms. Dropping mutation. "
            			+ "Keyspace {}, Column Family Ids {}", 
            			timeTaken, mutationTimeout, 
            			this.mutation.getKeyspaceName(), Arrays.toString(this.mutation.getColumnFamilyIds().toArray()));

If {{this.mutation == null}} then {{NullPointerException}} will be thrown, so we need to handle
that (sorry I was not clear before).

> 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: 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