You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/01/27 23:07:45 UTC

[jira] Updated: (CASSANDRA-2069) Read repair causes tremendous GC pressure

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

Jonathan Ellis updated CASSANDRA-2069:
--------------------------------------

    Fix Version/s: 0.7.2

> Read repair causes tremendous GC pressure
> -----------------------------------------
>
>                 Key: CASSANDRA-2069
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2069
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.1
>            Reporter: Brandon Williams
>             Fix For: 0.7.2
>
>
> To reproduce: start a three node cluster, insert 1M rows with stress.java and rf=2.  Take one down, delete its data, then bring it back up and issue 1M reads against it.  After the run is done you will see at least 1 STW long enough to mark the node as dead, often 4 or 5.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.