cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1292) Multiple migrations might run at once
Date Thu, 29 Jul 2010 13:15:17 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893605#action_12893605
] 

Hudson commented on CASSANDRA-1292:
-----------------------------------

Integrated in Cassandra #503 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/503/])
    run thrift and jmx migrations on migration stage. patch by gdusbabek, reviewed by stuhood.
CASSANDRA-1292


> Multiple migrations might run at once
> -------------------------------------
>
>                 Key: CASSANDRA-1292
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1292
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stu Hood
>            Assignee: Gary Dusbabek
>            Priority: Critical
>             Fix For: 0.7 beta 1
>
>         Attachments: 0001-run-thrift-and-jmx-migrations-on-to-migration-stage.patch
>
>
> The service.MigrationManager class manages a MIGRATION_STAGE where nodes should execute
db.migration.Migration instances.
> The problem is that the node that a client connects to via Thrift or Avro initiates the
migration in their client thread (calls migration.apply). Instead, the Thrift and Avro clients
should ensure that the migration occurs in MIGRATION_STAGE, and should block until the migration
is applied by the stage.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message