cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7601) Data loss after nodetool taketoken
Date Thu, 24 Jul 2014 14:48:39 GMT

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

Philip Thompson commented on CASSANDRA-7601:
--------------------------------------------

Wow, sorry about that Jake. I didn't run it on 1.2 and 2.0, I only checked to see if it was
in the list of failing tests on cassci. My mistake. If I switch to since('2.0') and update
the taketoken syntax, the test still fails because of data loss.

> Data loss after nodetool taketoken
> ----------------------------------
>
>                 Key: CASSANDRA-7601
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7601
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core, Tests
>         Environment: Mac OSX Mavericks. Ubuntu 14.04
>            Reporter: Philip Thompson
>            Priority: Minor
>         Attachments: consistent_bootstrap_test.py, taketoken.tar.gz
>
>
> The dtest consistent_bootstrap_test.py:TestBootstrapConsistency.consistent_reads_after_relocate_test
is failing on HEAD of the git branches 2.1 and 2.1.0. It is passing on 1.2 and 2.0.
> The test performs the following actions:
> - Create a cluster of 3 nodes
> - Create a keyspace with RF 2
> - Take node 3 down
> - Write 980 rows to node 2 with CL ONE
> - Flush node 2
> - Bring node 3 back up
> - Run nodetool taketoken on node 3 to transfer 80% of node 1's tokens to node 3
> - Check for data loss
> When the check for data loss is performed, only ~725 rows can be read via CL ALL.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message