You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org> on 2012/04/05 12:03:23 UTC
[jira] [Commented] (CASSANDRA-3629) Bootstrapping nodes don't
ensure schema is ready before continuing
[ https://issues.apache.org/jira/browse/CASSANDRA-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247118#comment-13247118 ]
Jonathan Ellis commented on CASSANDRA-3629:
-------------------------------------------
The easiest workaround for this is CASSANDRA-3600, which is also 1.0-only. That much should be safe to backport...
> 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