cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4115) UNREACHABLE schema after decommissioning a non-seed node
Date Thu, 12 Apr 2012 16:37:20 GMT

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

Brandon Williams commented on CASSANDRA-4115:
---------------------------------------------

This must be something with the environment, on 1.0 I see the node removed as soon as the
decom node begins to announce it has left (before it has completed announcing, and thus before
nodetool would even return) and it never reappears.
                
> UNREACHABLE schema after decommissioning a non-seed node
> --------------------------------------------------------
>
>                 Key: CASSANDRA-4115
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4115
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: ccm using the following unavailable_schema_test.py dtest.
>            Reporter: Tyler Patterson
>            Assignee: Brandon Williams
>            Priority: Minor
>         Attachments: 4115.txt
>
>
> decommission a non-seed node, sleep 30 seconds, then use thrift to check the schema.
UNREACHABLE is listed:
> {'75dc4c07-3c1a-3013-ad7d-11fb34208465': ['127.0.0.1'],
>  'UNREACHABLE': ['127.0.0.2']}

--
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

        

Mime
View raw message