cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8373) MOVED_NODE Topology Change event is never emitted
Date Fri, 19 Dec 2014 00:36:13 GMT


Tyler Hobbs commented on CASSANDRA-8373:

I looked into the single-node problem briefly and it wasn't clear how to fix things.  {{updateNormalTokens()}}
gets called frequently, which has the effect of removing nodes from the "moving" set.  Since
a single node moving isn't a terribly important case, I think it's worth committing what we
have and splitting that out.  I've opened CASSANDRA-8516 and assigned it to [~brandon.williams]
to take a look at.

> MOVED_NODE Topology Change event is never emitted
> -------------------------------------------------
>                 Key: CASSANDRA-8373
>                 URL:
>             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|]
call [changes the endpoint moving status|],
making the later isMoving conditional always false.

This message was sent by Atlassian JIRA

View raw message