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

Jonathan Ellis commented on CASSANDRA-4427:
-------------------------------------------

Here's what we were trying to address there:

bq. Now there is a actual new problem with 1.0.0. That problem is that when you 
start an initial cluster, i.e, when in 0.8 you would start node with 
auto-boostrap=false, you do often end up starting nodes simultaneously. That is 
why older version were using random token when auto-bootstrap was false. This 
problem does need to be fix for 1.0.0 because that is a serious regression. 
However, my argument is that even though we now default to auto-boostrap=true, 
that doesn't mean that there is no difference between setting up the initial 
nodes of a cluster and the latter bootstrapping of nodes to add capacity to an 
existing cluster. Indeed, in 1.0.0 we decided to draw this line based on 
whether a schema had been created or not (we call the bootstrap() method based 
on that). Imho, this means that we have no boostrap option and the "I have no 
schema" is the old auto-boostrap=false. So we should use random token in that 
case and balanced one otherwise the same way we are doing it in 
 0.8.
                
> Restarting a failed bootstrap instajoins the ring
> -------------------------------------------------
>
>                 Key: CASSANDRA-4427
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4427
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.0.11, 1.1.3
>
>         Attachments: 4427.txt
>
>
> I think when we made auto_bootstrap = true the default, we broke the check 
> for the bootstrap flag, creating a dangerous situation.

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

        

Reply via email to