You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/02/27 21:54:04 UTC
[jira] [Updated] (CASSANDRA-8516) NEW_NODE topology event emitted
instead of MOVED_NODE by moving node
[ https://issues.apache.org/jira/browse/CASSANDRA-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tyler Hobbs updated CASSANDRA-8516:
-----------------------------------
Summary: NEW_NODE topology event emitted instead of MOVED_NODE by moving node (was: NEW_NODE topology event emitted instead of MOVED_NODE in a one node cluster)
> NEW_NODE topology event emitted instead of MOVED_NODE by moving node
> --------------------------------------------------------------------
>
> Key: CASSANDRA-8516
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8516
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Stefania
> Priority: Minor
> Fix For: 2.0.13
>
>
> As discovered in CASSANDRA-8373, when you move a node in a single-node cluster, a {{NEW_NODE}} event is generated instead of a {{MOVED_NODE}} event.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)