cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10293) Re-populate token metadata after commit log replay
Date Thu, 26 Nov 2015 14:04:11 GMT

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

Paulo Motta updated CASSANDRA-10293:
------------------------------------
    Component/s: Lifecycle
                 Coordination

> 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
>          Components: Coordination, Lifecycle
>            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)

Mime
View raw message