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] [Updated] (CASSANDRA-4427) Restarting a failed bootstrap instajoins the ring
Date Thu, 12 Jul 2012 19:21:34 GMT

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

Brandon Williams updated CASSANDRA-4427:
----------------------------------------

    Attachment: 4427.txt

Patch to remove the check for non-system tables.  As far as I can tell, it makes no sense
to have this condition, since you can partially stream some data during bootstrap, then die.
 If you try again without clearing the machine, instajoin.

It looks like this condition was added as part of a fix for CASSANDRA-3219 in commit de829f17,
but the check was inverted and later fixed in CASSANDRA-3285.  However, the reasoning behind
having such a check at all is never explained and I can't see why it should be there.
                
> 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

        

Mime
View raw message