cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2163) UnavailableException after bootstrapping a previously decommissioned node
Date Mon, 14 Feb 2011 21:59:57 GMT

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

Brandon Williams commented on CASSANDRA-2163:
---------------------------------------------

Unable to repro with r1070628, but I did make some gossiper changes there forward-porting
CASSANDRA-2115 so maybe I struck gold.

> UnavailableException after bootstrapping a previously decommissioned node
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2163
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2163
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8
>            Reporter: Sylvain Lebresne
>            Assignee: Brandon Williams
>
> In trunk (not in 0.7), if I boostrap a node, decommission it and boostrap it back (after
having clean all data directory but on same ip), I get UnavailableException on read. 
> I've bisected the regression to r1067508.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message