[jira] [Commented] (CASSANDRA-4564) MoveTest madness

["Liu Yu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536815#comment-13536815 ] 

Liu Yu commented on CASSANDRA-4564:
-----------------------------------

For the second issue, the root cause is: the key token is endpointToken+5, and the endpoint token is moved to endpointToken+2, so there is no key need to be moved. I have changed the move token to enpointToken+7 and updated the test cases.
                
> MoveTest madness
> ----------------
>
>                 Key: CASSANDRA-4564
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4564
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Eric Evans
>              Labels: lhf
>
> 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