Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 4 Jan 2013 13:42:13 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12604290.1345587427282.80431.1357306933097@arcas>
In-Reply-To: <JIRA.12604290.1345587427282@arcas>
References: <JIRA.12604290.1345587427282@arcas>
Subject: [jira] [Updated] (CASSANDRA-4564) MoveTest madness
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams updated CASSANDRA-4564:
----------------------------------------

    Fix Version/s: 1.2.1
    
> MoveTest madness
> ----------------
>
>                 Key: CASSANDRA-4564
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4564
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.1.7
>            Reporter: Eric Evans
>            Assignee: Liu Yu
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1.9, 1.2.1
>
>         Attachments: cassandra-1.1-4564.txt
>
>
> I encountered what looks like bugs in {{o.a.c.service.MoveTest.newTestWriteEndpointsDuringMove()}} while doing something else; Here is a (poorly researched )ticket before I forget :)
> * There are two loops over non-system tables, and the first is a NOOP
> * In the second loop, a set exactly {{replicationFactor}} in size is compared against {{tmd.getWriteEndpoints()}}, which should produce greater than {{replicationFactor}} endpoints during a move (shouldn't it?); How does this pass?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira