[ https://issues.apache.org/jira/browse/CASSANDRA-10580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049489#comment-15049489 ]
Anubhav Kale commented on CASSANDRA-10580: ------------------------------------------ Thanks for the review. I will work on the patches. Quick Question about the Null Ref Exception on empty constructors. I did not see this happen in my local run. Are you suggesting this is a pattern enforced by logging library and therefore, I should have constructor with (say) bool arg, and use that wherever I was using default constructor ? Sorry, I just am not clear on why something like this necessary. > On dropped mutations, more details should be logged. > ---------------------------------------------------- > > Key: CASSANDRA-10580 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10580 > 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 StorageProxy.java and MessagingTask.java. I > will submit a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)