You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tuukka Luolamo (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/10/12 02:49:11 UTC

[jira] [Issue Comment Edited] (CASSANDRA-3351) If node fails to join a ring it will stay in joining state indefinately

    [ https://issues.apache.org/jira/browse/CASSANDRA-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125506#comment-13125506 ] 

Tuukka Luolamo edited comment on CASSANDRA-3351 at 10/12/11 12:48 AM:
----------------------------------------------------------------------

Also per driftx I ran gms trace and grabbed about 1 minute worth of log entries that I have attached here. Problem node ip is 10.82.211.8
                
      was (Author: tuke):
    Also per driftx I ran gms trace and grabbed about 1 minute worth of log entries that I have attached here.
                  
> If node fails to join a ring it will stay in joining state indefinately
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-3351
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3351
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.6
>         Environment: xlarge ec2, Ubuntu 11.04 Natty, JNA
>            Reporter: Tuukka Luolamo
>            Assignee: Brandon Williams
>            Priority: Trivial
>              Labels: nodetool
>         Attachments: cassandra.log.gz
>
>
> While attempting to add a new node to my ring something went wrong and I had to terminate the node on ec2. After this the node keeps appearing in the ring command in "joining" state and never goes away. Per driftx on the Cassandra channel if I do a whole cluster restart it should go away, but since this is a production system this is not really possible. Additionally if I could join a node with same IP again this should go away, but being on ec2 this is not always easy. So not sure if this truly qualifies as a bug or more like a feature request, but I feel there should be a way to remove a node in any state if I wish without joining a node with same ip or doing a whole cluster restart.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira