cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-1391) Allow Concurrent Schema Migrations
Date Sat, 20 Aug 2011 20:24:27 GMT


Pavel Yaskevich updated CASSANDRA-1391:

    Attachment: 0001-CASSANDRA-1391-refactoring-of-the-DatabaseDescriptor.patch

Moved all static collections that hold information about schema from DatabaseDescriptor/CFMetaData/Table
classes to union o.a.c.config.DBSchema class (also refactored o.a.c.db.migration classes to
support that change), that also will enable us to apply schema migrations in the isolated

> Allow Concurrent Schema Migrations
> ----------------------------------
>                 Key: CASSANDRA-1391
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Pavel Yaskevich
>             Fix For: 1.0
>         Attachments: 0001-CASSANDRA-1391-refactoring-of-the-DatabaseDescriptor.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:


View raw message