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

Posted to commits@cassandra.apache.org by "sankalp kohli (JIRA)" <ji...@apache.org> on 2014/02/15 00:31:21 UTC

[jira] [Commented] (CASSANDRA-6616) Nodetool repair is taking a long time.

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

sankalp kohli commented on CASSANDRA-6616:
------------------------------------------

CASSANDRA-6455 will fix this problem as the JIRA will allow multiple CFs to run in parallel. 


> 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)