[
https://issues.apache.org/jira/browse/CASSANDRA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990392#comment-12990392
]
Brandon Williams commented on CASSANDRA-2069:
---------------------------------------------
Bisecting this indicates two problems. First, the tremendous GC pressure
doesn't exhibit until we increase the newgen size. If that is ignored and we
only observe whether stress.java moves forward (it has the 'keep trying' rather
than 'keep going' behavior) then the culprit is r1053245.
Both cases show that RR requests can grow unbounded, which is probably ok, but
if it's the same request over and over we still queue it as many times as it's
requested.
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
