[
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 dropped. (was: When
mutations are dropped, the column family should be printed / have a counter per
column family)
> On dropped mutations, more details should be dropped.
> -----------------------------------------------------
>
> Key: CASSANDRA-10580
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10580
> Project: Cassandra
> Issue Type: New Feature
> 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. 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 easy, and I will submit a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
