Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Fix Version/s: 1.1.0
    • Component/s: None
    • Labels:
      None

      Description

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

        Attachments

        1. CASSANDRA-1391-v2.patch
          212 kB
          Pavel Yaskevich
        2. CASSANDRA-1391.patch
          200 kB
          Pavel Yaskevich
        3. 1391-rebased.txt
          205 kB
          Jonathan Ellis
        4. 0002-CASSANDRA-1391-fixes.patch
          28 kB
          Pavel Yaskevich
        5. 0001-CASSANDRA-1391-main.patch
          203 kB
          Pavel Yaskevich

          Issue Links

            Activity

              People

              • Assignee:
                xedin Pavel Yaskevich
                Reporter:
                stuhood Stu Hood
                Reviewer:
                Jonathan Ellis
              • Votes:
                3 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: