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

Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2011/02/15 09:17:01 UTC

[jira] Resolved: (CASSANDRA-2163) UnavailableException after bootstrapping a previously decommissioned node

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

Sylvain Lebresne resolved CASSANDRA-2163.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8

> 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
>             Fix For: 0.8
>
>
> 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