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

Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2015/10/09 03:59:26 UTC

[jira] [Updated] (CASSANDRA-10293) Re-populate token metadata after commit log replay

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

Paulo Motta updated CASSANDRA-10293:
------------------------------------
    Summary: Re-populate token metadata after commit log replay  (was: A node down is not always displayed in nodetool status )

> Re-populate token metadata after commit log replay
> --------------------------------------------------
>
>                 Key: CASSANDRA-10293
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10293
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Assignee: Paulo Motta
>            Priority: Minor
>             Fix For: 3.0.0 rc2
>
>         Attachments: mv_repair_test.sh
>
>
> I've noticed this while working on another task: a node that was currently down was not showed in my nodetool status. The node had joined the cluster and was displayed in the status before.
> I've attached [^mv_repair_test.sh] to reproduce the issue. After the execution of the script, just try a: ccm node3 nodetool status



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)