You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2015/01/20 18:09:46 UTC

[jira] [Updated] (CASSANDRA-8516) NEW_NODE topology event emitted instead of MOVED_NODE in a one node cluster

     [ https://issues.apache.org/jira/browse/CASSANDRA-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani updated CASSANDRA-8516:
--------------------------------------
    Fix Version/s:     (was: 2.0.12)
                   2.0.13

> NEW_NODE topology event emitted instead of MOVED_NODE in a one node cluster
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8516
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8516
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Brandon Williams
>            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)