[
https://issues.apache.org/jira/browse/CASSANDRA-10580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anubhav Kale updated CASSANDRA-10580:
-------------------------------------
Summary: On dropped mutations, more details should be logged. (was: On
dropped mutations, more details should be dropped.)
> On dropped mutations, more details should be logged.
> ----------------------------------------------------
>
> Key: CASSANDRA-10580
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10580
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Production
> Reporter: Anubhav Kale
> Priority: Minor
> Fix For: 2.1.x
>
>
> 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 will need to be done in StorageProxy.java and MessagingTask.java.
> It is straightforward, and I will submit a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
