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
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.
-
You can reply to this email to add a comment to the issue online.
