[ 
https://issues.apache.org/jira/browse/CASSANDRA-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881426#comment-13881426
 ] 

Brandon Williams commented on CASSANDRA-6616:
---------------------------------------------

This is because the CFs are being processed sequentially. CASSANDRA-6566 may 
help some, but if all of these CFs did have data, processing them in parallel 
would be detrimental to IO.  It would be better to have much less CFs.

> Nodetool repair is taking a long time. 
> ---------------------------------------
>
>                 Key: CASSANDRA-6616
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6616
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Cassandra Version 2.0.4 running on Redhat Version 6
>            Reporter: Dharsan Logendran
>
> We have a two  nodes cluster with the replication factor of 2.   The db has 
> more than 2500 column families(tables).   The 'nodetool -pr -par' repair on 
> an empty database(one or table has a litter data) takes about 30 hours to 
> complete.  
>  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to