[
https://issues.apache.org/jira/browse/CASSANDRA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064637#comment-13064637
]
Jonathan Ellis commented on CASSANDRA-1391:
-------------------------------------------
bq. A lamport-ish clock consisting of node name and counter/timestamp would
probably be sufficient for ordering
That would probably work too, although it feels weird to base it on who
generated the migration, rather than the migration contents.
bq. we'd have to trust that nodes would be doing the right thing (by applying
migrations) independently after the quarantine is over
Right. I'm totally comfortable with this, feels like a good fit with how the
rest of the system works.
> 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: Gary Dusbabek
>
> 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
