[ https://issues.apache.org/jira/browse/CASSANDRA-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Holmberg reassigned CASSANDRA-8373: ---------------------------------------- Assignee: (was: Adam Holmberg) A quick check shows that NEW event emitting for a move in single-node clusters in 2.1 as well, independent of this patch. Interesting anomaly, but seems unrelated to the change I was proposing. With my current priorities, I'm not sure when I'll be able to dig into the secondary issue. I'm un-assigning for now. > 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 > 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)