cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-1391) Allow Concurrent Schema Migrations
Date Wed, 14 Dec 2011 11:41:31 GMT

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

Pavel Yaskevich edited comment on CASSANDRA-1391 at 12/14/11 11:40 AM:
-----------------------------------------------------------------------

I figured out that we don't really need "lastVersion" field in Migration class anymore so
it's now removed. I have removed migration ordering validation from DefinitionsUpdateVerbHandler
and fixed nit you mentioned. Also I think that we still need versions to be of TimeUUID type
because it's useful for example in MigrationManager.rectify were we need to know if and what
migrations do we want to send to others.
                
      was (Author: xedin):
    I figured out that we don't really need "oldVersion" field anymore so it's now removed.
I have removed migration ordering validation from DefinitionsUpdateVerbHandler and fixed nit
you mentioned. Also I think that we still need versions to be of TimeUUID type because it's
useful for example in MigrationManager.rectify were we need to know if and what migrations
do we want to send to others.
                  
> Allow Concurrent Schema Migrations
> ----------------------------------
>
>                 Key: CASSANDRA-1391
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1391
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Stu Hood
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1
>
>         Attachments: 0001-new-migration-schema-and-avro-methods-cleanup.patch, 0002-avro-removal.patch,
0003-oldVersion-removed-nit-fixed.patch, CASSANDRA-1391.patch
>
>
> CASSANDRA-1292 fixed multiple migrations started from the same node to properly queue
themselves, but it is still possible for migrations initiated on different nodes to conflict
and leave the cluster in a bad state. Since the system_add/drop/rename methods are accessible
directly from the client API, they should be completely safe for concurrent use.
> It should be possible to allow for most types of concurrent migrations by converting
the UUID schema ID into a VersionVectorClock (as provided by CASSANDRA-580).

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