cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1216) removetoken drops node from ring before re-replicating its data is finished
Date Wed, 25 Aug 2010 16:40:16 GMT


Nick Bailey commented on CASSANDRA-1216:

Re: timeouts

Yes I'm just not sure how to approach determining the right values for these.  Depends mostly
on the amount of data and network bandwidth.

Re: RemoveTest

Yeah. The message sink in the test immediately responds to the stream request saying there
are no files to stream.  This makes the StreamInManager think the data didn't exist remotely.
 Doing it that way seems much easier than trying to make the test actually stream something.

> removetoken drops node from ring before re-replicating its data is finished
> ---------------------------------------------------------------------------
>                 Key: CASSANDRA-1216
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Nick Bailey
>             Fix For: 0.7 beta 2
>         Attachments: 0001-Add-callbacks-to-streaming.patch, 0002-Modify-removeToken-to-be-similar-to-decommission.patch,
0003-Fixes-to-old-tests.patch, 0004-Additional-tests-for-removeToken.patch
> this means that if something goes wrong during the re-replication (e.g. a source node
is restarted) there is (a) no indication that anything has gone wrong and (b) no way to restart
the process (other than the Big Hammer of running repair)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message