[
https://issues.apache.org/jira/browse/CASSANDRA-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339489#comment-14339489
]
Stefania commented on CASSANDRA-8516:
-------------------------------------
At [~thobbs], I think that the problematic call to {{updateNormalTokens}} is in
SS.{{setTokens()}}:
Is it possible to rely on {{StorageService.operatingMode}} ({{Mode.MOVING}})
instead of or along with the moving tokens? I works if we call move on the
local node but does it get called in other contexts too (e.g. Gossip)?
Also, I reproduced the problem with {{nodetool move 123}} but I kept on getting
the exception below, which I could only bypass it by commenting it out:
{code}
if (getTokenMetadata().getTokens(localAddress).size() > 1)
{
logger.error("Invalid request to move(Token); This node has more than
one token and cannot be moved thusly.");
throw new UnsupportedOperationException("This node has more than one
token and cannot be moved thusly.");
}
{code}
Could I have the correct command or config to reproduce this issue on 2.1 along
with any other suggested tests (single node / multiple node clusters), and do
we need to test drivers too or is it enough to check that we call {{onMove}}
rather than {{onJoinCluster}} in SS.{{handleStateNormal}}.
Thanks!
> 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)
