[ https://issues.apache.org/jira/browse/CASSANDRA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1292: ------------------------------------- Attachment: 0001-run-thrift-and-jmx-migrations-on-to-migration-stage.patch > 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.0 > > 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.