[
https://issues.apache.org/jira/browse/CASSANDRA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990416#comment-12990416
]
Matthew F. Dennis commented on CASSANDRA-2069:
----------------------------------------------
I've observed similar issues with large a large newgen, largish memtables and
writing at RF>1 at CL.Q/CL.ALL though it's not as immediate as it is with RR.
We should look into a way at bounding the number of outstanding requests (RR or
"send to replica"), or more aggressively timing out the older requests once we
hit some configurable threshold of outstanding requests.
> 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
