[
https://issues.apache.org/jira/browse/CASSANDRA-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339560#comment-14339560
]
Brandon Williams commented on CASSANDRA-8516:
---------------------------------------------
bq. Also, I reproduced the problem with nodetool move 123 but I kept on getting
the exception below
You need to set num_tokens: 1 in the yaml, vnodes don't support move.
> 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: 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)
