cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3629) Bootstrapping nodes don't ensure schema is ready before continuing
Date Wed, 14 Dec 2011 18:47:30 GMT

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

Brandon Williams commented on CASSANDRA-3629:
---------------------------------------------

bq. should we put this in 0.8.9 as well?

The 0.8.9 ship looks sailed unless we want to reroll for this, do you mean 0.8.10?

Committed to 1.0, the 0.8 backport isn't trivial in any case, so leaving the ticket open for
that.
                
> Bootstrapping nodes don't ensure schema is ready before continuing
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-3629
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3629
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.0.7
>
>         Attachments: 0001-Wait-until-the-highest-known-schema-has-been-reached.txt
>
>
> A bootstrapping node will assume that after it has slept for RING_DELAY it has all of
the schema migrations and can continue the bootstrap process.  However, with a large enough
amount of migrations this is not sufficient and causes problems.

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