cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dharsan Logendran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6616) Nodetool repair is taking a long time.
Date Mon, 27 Jan 2014 20:32:37 GMT

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

Dharsan Logendran commented on CASSANDRA-6616:
----------------------------------------------

Thanks Brandon,

Is there any  easy way in C* finding out which tables are empty. I don't want run count on
each table to find out which ones are empty.

Dharsan

 



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

Mime
View raw message