[
https://issues.apache.org/jira/browse/CASSANDRA-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984416#action_12984416
]
Brandon Williams commented on CASSANDRA-1934:
---------------------------------------------
Yes it will. endpoint is the node entering the ring, currentNode is the node
that currently has the token passed in (which in this case will be endpoint's
token also), but does not mean 'my address' to the node making the evaluation.
Thus, if we see the same endpoint and token, we do nothing in the current code,
causing the state to never get updated.
> Update token metadata for NORMAL state
> --------------------------------------
>
> Key: CASSANDRA-1934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1934
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0 rc 3
> Reporter: Nick Bailey
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 0.7.1
>
> Attachments: 1934.txt
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The handleStateNormal() method in StorageService.java doesn't update the
> tokenmetadata. This means if you try to decommission a node but for some
> reason it fails, and then you bring the node back up, all other nodes will
> see it in a 'Leaving' state. When the state jumps back to normal they should
> update the token metadata to reflect that.
> This also means you won't be able to call 'removetoken' on that node, unless
> you restart another node in the cluster in order to put it back in a 'normal'
> state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
