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

Posted to commits@cassandra.apache.org by "Sean Bridges (JIRA)" <ji...@apache.org> on 2014/10/23 21:43:35 UTC

[jira] [Created] (CASSANDRA-8177) sequential repair is much more expensive than parallel repair

Sean Bridges created CASSANDRA-8177:
---------------------------------------

             Summary: 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


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)