cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CASSANDRA-7601) Data loss after nodetool taketoken
Date Tue, 02 Sep 2014 17:45:21 GMT

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

Michael Shuler reopened CASSANDRA-7601:
---------------------------------------

It appears that cassandra-shuffle has reappeared in the 2.1.0, 2.1, and trunk branches. `git
log` isn't helpful to see where this was re-added.

> 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
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 1.2.19, 2.0.10, 2.1 rc5
>
>         Attachments: 7601-1.2.txt, 7601-2.0.txt, 7601-2.1.txt, 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.
> 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.3.4#6332)

Mime
View raw message