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/14 20:31:58 UTC
[jira] Created: (CASSANDRA-2163) UnavailableException after
bootstrapping a previously decommissioned node
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
[jira] Commented: (CASSANDRA-2163) UnavailableException after
bootstrapping a previously decommissioned node
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994684#comment-12994684 ]
Sylvain Lebresne commented on CASSANDRA-2163:
---------------------------------------------
I confirm I cannot repro now either. The forward port of CASSANDRA-2115 apparently fixed whatever was wrong.
> 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
[jira] Resolved: (CASSANDRA-2163) UnavailableException after
bootstrapping a previously decommissioned node
Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (CASSANDRA-2163) UnavailableException after
bootstrapping a previously decommissioned node
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (CASSANDRA-2163) UnavailableException after
bootstrapping a previously decommissioned node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2163:
--------------------------------------
Remaining Estimate: 1h
Original Estimate: 1h
> 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
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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