cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1359) Inconsistent ring view after notetool-move
Date Wed, 04 Aug 2010 20:10:45 GMT

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

Jonathan Ellis commented on CASSANDRA-1359:
-------------------------------------------

Please test 0.6.4

> Inconsistent ring view after notetool-move
> ------------------------------------------
>
>                 Key: CASSANDRA-1359
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1359
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.2
>            Reporter: Ran Tavory
>
> After running nodetool move, the move operation succeeds but different hosts on the ring
have a different view of the tokens.
> The moved node has the correct view but all other nodes have incorrect views. They still
see the moved node at it's previous position on the ring, not the new one.
> I've waited a few minutes but it doesn't help, only restarting the moved nodes make other
members realize it's new and correct position.
> At least in my setup it was 100% repro (I moved 5 nodes and each time same story). I'm
using 0.6.2.
> See thread here http://www.mail-archive.com/user@cassandra.apache.org/msg04978.html
> Here's the view from nodetool ring after the move operation completed successfully:
> The moved node sees this (note the position of 192.168.254.58):
> (ob1124)(cassandra@cass24:apache-cassandra-0.6.2)$ nodetool -h 192.168.254.58 -p 9004
ring
> Address       Status     Load          Range                                      Ring
>                                        170141183460469231731687303715884105727
> 192.168.252.88Up         5.7 GB        14131484407726020523932116250949797205     |<--|
> 192.168.252.124Up         2.44 GB       56713727820156410577229101238628035242     |
  ^
> 192.168.254.58Up         8.13 GB       113427455640312821154458202477256070484    v 
 |
> 192.168.254.57Up         6.52 GB       113427455640312821154458202477256070485    | 
 ^
> 192.168.252.125Up         6.52 GB       141784319550391026443072753096570088105    v
  |
> 192.168.254.59Up         1.63 GB       170141183460469231731687303715884105727    |-->|
> While other nodes see this (again, note the position of 192.168.254.58):
> (ob1124)(cassandra@cass24:apache-cassandra-0.6.2)$ nodetool -h 192.168.252.124 -p 9004
ring
> Address       Status     Load          Range                                      Ring
>                                        170141183460469231731687303715884105727
> 192.168.252.88Up         5.7 GB        14131484407726020523932116250949797205     |<--|
> 192.168.252.124Up         2.46 GB       56713727820156410577229101238628035242     |
  ^
> 192.168.254.57Up         6.52 GB       113427455640312821154458202477256070485    v 
 |
> 192.168.252.125Up         6.52 GB       141784319550391026443072753096570088105    |
  ^
> 192.168.254.58Up         1.63 GB       141784319550391026443072753096570088106    v 
 |
> 192.168.254.59Up         1.63 GB       170141183460469231731687303715884105727    |-->|

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


Mime
View raw message