[
https://issues.apache.org/jira/browse/CASSANDRA-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872954#action_12872954
]
Hudson commented on CASSANDRA-987:
----------------------------------
Integrated in Cassandra #448 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/448/])
apply CASSANDRA-987 to thrift.CassandraDaemon too...
...and expect that lastMigration might be null
Patch by eevans
> We need a way to recover from a crash during migration if the crash happens
> before 'definitions' are flushed.
> -------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-987
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.7
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Fix For: 0.7
>
> Attachments:
> 0001-apply-CASSANDRA-987-to-thrift.CassandraDaemon-too.patch,
> 0001-recover-when-a-migration-crashes-before-system-table.patch
>
>
> Because what happens is this: the schema exists only in the commit log and
> so will not be loaded during initialization. The schema sstables will then
> be written during CL recovery, but the changes never applied. This could all
> be resolved with another restart, but I'd like to find a better way. This
> shouldn't be too hard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
