[ https://issues.apache.org/jira/browse/CASSANDRA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934938#comment-13934938 ]
Yuki Morishita commented on CASSANDRA-6852: ------------------------------------------- [~cscetbon] Did you specify your keyspace when showing the ring? The output looks like it didn't. {code} $ nodetool status ks1 {code} should show you dc3 owns 0% for ks1. > can't repair -pr part of data when not replicating data everywhere (multiDCs) > ----------------------------------------------------------------------------- > > Key: CASSANDRA-6852 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6852 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Cyril Scetbon > Labels: multi-dcs, ranges, repair > > Our environment is as follows : > - 3 DCS : dc1,dc2 and dc3 > - replicate all keyspaces to dc1 and dc2 > - replicate a few keyspaces to dc3 as we have less hardware and use it for > computing statistics > We use repair -pr everywhere regularly. FYI, a full repair takes almost 20 > hours per node. The matter is that we can't use "repair -pr" anymore for > tokens stored on dc3 concerning keyspaces not replicated. We should have a > way to repair those ranges without doing a FULL REPAIR everywhere -- This message was sent by Atlassian JIRA (v6.2#6252)