Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 13 Mar 2014 14:21:46 +0000 (UTC)
From: "Yuki Morishita (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12701211.1394708615555.59559.1394720506939@arcas>
In-Reply-To: <JIRA.12701211.1394708615555@arcas>
References: <JIRA.12701211.1394708615555@arcas>
Subject: [jira] [Resolved] (CASSANDRA-6852) can't repair -pr part of data
 when not replicating data everywhere (multiDCs)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yuki Morishita resolved CASSANDRA-6852.
---------------------------------------

    Resolution: Duplicate

See CASSANDRA-5424

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