[ https://issues.apache.org/jira/browse/CASSANDRA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095206#comment-13095206 ]
Pavel Yaskevich commented on CASSANDRA-1391: -------------------------------------------- Isolated flag is used to indicate that migration will be applied using isolated schema so SystemTable.Schema record for LAST_MIGRATION_KEY won't be updated and no real file operations will be made. This allows us to old deserialize migrations and re-apply them one-by-one to in case on merging migration (after each re-apply information about that migration going to be updated in SystemTable.Schema and SystemTable.Migrations). > Allow Concurrent Schema Migrations > ---------------------------------- > > Key: CASSANDRA-1391 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1391 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Stu Hood > Assignee: Pavel Yaskevich > Fix For: 1.0 > > Attachments: 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. For more information on JIRA, see: http://www.atlassian.com/software/jira