You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/03/15 01:08:00 UTC

[jira] [Updated] (CASSANDRA-16517) Cassandra dropped read message and dropped mutation message

     [ https://issues.apache.org/jira/browse/CASSANDRA-16517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-16517:
-----------------------------------------
    Resolution: Invalid
        Status: Resolved  (was: Triage Needed)

This jira is for tracking bugs, not support.  I recommend contacting the slack or user mailing list through https://cassandra.apache.org/community/ for assistance.

> Cassandra dropped read message and dropped mutation message
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-16517
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16517
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Build, Consistency/Repair, Messaging/Internode
>            Reporter: Dmitry
>            Priority: Normal
>
> We have a Cassandra cluster consisting of 6 catches (rhel 7.8). A dropped read message and a dropped mutation message appear on two nodes of our DBMS.
> We check it using tpstats. Tried changing the GC mechanism to g1 and Increasing the timeouts.
> How to fix it



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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