[
https://issues.apache.org/jira/browse/CASSANDRA-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990433#comment-12990433
]
Jonathan Ellis commented on CASSANDRA-2069:
-------------------------------------------
Working on another approach that should let us throw away repair handlers in
the expected case that everyone responds quickly. This will be kinder to new
gen gc since we won't have nearly as many survivors.
> 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
> Assignee: Jonathan Ellis
> Fix For: 0.7.2
>
> Attachments: 2069.txt
>
>
> 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
