cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8373) MOVED_NODE Topology Change event is never emitted
Date Tue, 02 Dec 2014 19:53:12 GMT

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

Tyler Hobbs commented on CASSANDRA-8373:
----------------------------------------

On 2.0, this gives the correct behavior with a multi-node cluster, but with a single-node
cluster a {{NEW_NODE}} notification is sent instead of a {{MOVED_NODE}} notification.  It
looks the single-node behavior is also present in 2.0, but it would be nice to fix that here
as well.

> MOVED_NODE Topology Change event is never emitted
> -------------------------------------------------
>
>                 Key: CASSANDRA-8373
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8373
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Adam Holmberg
>            Assignee: Adam Holmberg
>            Priority: Minor
>             Fix For: 2.0.12, 2.1.3
>
>         Attachments: 8373.txt
>
>
> lifeCycleSubscribers.onMove never gets called because [this tokenMetadata.updateNormalTokens|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageService.java#L1585]
call [changes the endpoint moving status|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/locator/TokenMetadata.java#L190],
making the later isMoving conditional always false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message