[jira] [Commented] (CASSANDRA-10864) Dropped mutations high until cluster restart

["Jeff Jirsa (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290289#comment-16290289 ] 

Jeff Jirsa commented on CASSANDRA-10864:
----------------------------------------

[~autocracy] / [~yukim] / [~mambocab] - do any of you have any new information on this issue? It's been quite some time, and it's listed as impacting a nearly EOL branch. Should we keep this open? If there's no response, I propose we close this as wontfix until/unless someone demonstrates it is still a problem on the active branches.

> Dropped mutations high until cluster restart
> --------------------------------------------
>
>                 Key: CASSANDRA-10864
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10864
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeff Ferland
>              Labels: proposed-wontfix
>
> Originally raised and investigated in https://www.mail-archive.com/user@cassandra.apache.org/msg44586.html
> Cause is still unclear, but a rolling restart has on two occasions since been performed to cope with dropped mutations and timed-out reads.
> Pattern is indicative of some kind of code quality issue possibly involving locking operations. Stack flame graphs do not show a clear difference between restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org