cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1391) Allow Concurrent Schema Migrations
Date Fri, 11 Nov 2011 18:48:52 GMT


T Jake Luciani commented on CASSANDRA-1391:

I think the patch is a good start but I do like Jonathans idea of moving to native CFs too.

We just want to make sure this gets into 1.1 since it's a problem a lot of people run into.

Regarding the current impl, my concern is missing fields added to migration structs over time.
like we had happen a lot in CFMetaData conversion code.

Could you add a test verifies all migration struct fields are accounted for in the merge logic?
so if someone adds a new field and doesn't update the migration merge logic it would cause
this test to fail

> Allow Concurrent Schema Migrations
> ----------------------------------
>                 Key: CASSANDRA-1391
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Stu Hood
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message