Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 17 Nov 2011 19:39:51 +0000 (UTC)
From: "Vijay (Resolved) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1989636920.39866.1321558791606.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1947386931.39496.1321554711200.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CASSANDRA-3502) Repair of one CF streams data of
 the other CF's
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vijay resolved CASSANDRA-3502.
------------------------------

    Resolution: Duplicate

Was actually looking at 0.8.6 patch and thinking of fixing it. seems like it is fixed in 1.0.0
                
> Repair of one CF streams data of the other CF's
> -----------------------------------------------
>
>                 Key: CASSANDRA-3502
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3502
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.1
>
>
> Currently Manual Repair on a cf with inconsistent data will stream those ranges for all the CF's in the keyspace. 
> StreamIn.requestRanges() just takes table name as a argument and requests inconsistent ranges for all the CF's within a keyspace.
> The expected behaviour is to stream only the CF's Ranges.
> This trigger a lot more compaction of the CF's which are not inconsistent and a lot more traffic between the nodes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira