[
https://issues.apache.org/jira/browse/CASSANDRA-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247353#comment-13247353
]
Joaquin Casares edited comment on CASSANDRA-3629 at 4/9/12 6:02 PM:
--------------------------------------------------------------------
A valid workaround for 0.8 is to save your current schema, move all Mutation
and Schema sstables from all nodes to another directory (for temporary backup),
stop all nodes, restart one seed node, paste the old schema (to create the
first mutation and recreate the schema), restart that node one more time, then
start the rest of the nodes.
was (Author: j.casares):
A valid workaround for 0.8 is to save your current schema, move all
Mutation and Schema sstables from all nodes to another directory (for temporary
backup), stop all nodes, restart one seed node, paste the old schema (to create
the first mutation and recreate the schema), then start the rest of the nodes.
> 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
