cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-987) We need a way to recover from a crash during migration if the crash happens before 'definitions' are flushed.
Date Sat, 22 May 2010 12:43:19 GMT

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

Hudson commented on CASSANDRA-987:
----------------------------------

Integrated in Cassandra #443 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/443/])
    recover when a migration crashes before system table is flushed. patch by gdusbabek, reviewed
by stuhood. CASSANDRA-987


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


Mime
View raw message