[
https://issues.apache.org/jira/browse/CASSANDRA-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-8177.
---------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.1.3)
Assignee: (was: Yuki Morishita)
I think this is sufficiently addressed by CASSANDRA-7024 and CASSANDRA-8193.
> sequential repair is much more expensive than parallel repair
> -------------------------------------------------------------
>
> Key: CASSANDRA-8177
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8177
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sean Bridges
> Attachments: cassc-week.png, iostats.png
>
>
> This is with 2.0.10
> The attached graph shows io read/write throughput (as measured with iostat)
> when doing repairs.
> The large hump on the left is a sequential repair of one node. The two much
> smaller peaks on the right are parallel repairs.
> This is a 3 node cluster using vnodes (I know vnodes on small clusters isn't
> recommended). Cassandra reports load of 40 gigs.
> We noticed a similar problem with a larger cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
