cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6852) can't repair -pr part of data when not replicating data everywhere (multiDCs)
Date Tue, 18 Mar 2014 17:11:43 GMT


Yuki Morishita commented on CASSANDRA-6852:


You mean you want to know in which node the specific key is stored?

You can use the following JMX operations to find out:


getNaturalEndpoints(keyspace, columnfamily, key): returns the endpoint address where specified
key in ks/cf is stored.
getRangeToEndpointMap(keyspace): returns the range to endpoints map for given keyspace.

> can't repair -pr part of data when not replicating data everywhere (multiDCs)
> -----------------------------------------------------------------------------
>                 Key: CASSANDRA-6852
>                 URL:
>             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
> 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

View raw message