[
https://issues.apache.org/jira/browse/CASSANDRA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Bailey updated CASSANDRA-1650:
-----------------------------------
Attachment: 0001-Don-t-wait-for-confirmation-when-replication-factor-.patch
When replication factor is 1 it is impossible to recover data so we shouldn't
wait for confirmation.
> removetoken is broken
> ---------------------
>
> Key: CASSANDRA-1650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1650
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Brandon Williams
> Fix For: 0.7.0
>
> Attachments:
> 0001-Don-t-wait-for-confirmation-when-replication-factor-.patch
>
>
> When running removetoken on a dead node, it hangs forever. The debug log
> shows:
> DEBUG 19:45:53,794 Node /10.179.111.137 ranges
> [(115049868157599339472315320703867977321,62676456546693435176060154681903071729]]
> DEBUG 19:45:53,795 Range
> (115049868157599339472315320703867977321,62676456546693435176060154681903071729]
> will be responsibility of cassandra-1/10.179.65.102
> DEBUG 19:45:53,798 Pending ranges:
> cassandra-1/10.179.65.102:(115049868157599339472315320703867977321,62676456546693435176060154681903071729]
> DEBUG 19:45:53,798 Node /10.179.111.137 ranges
> [(115049868157599339472315320703867977321,62676456546693435176060154681903071729]]
> DEBUG 19:45:53,799 Range
> (115049868157599339472315320703867977321,62676456546693435176060154681903071729]
> will be responsibility of cassandra-1/10.179.65.102
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
