You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2010/07/16 23:59:49 UTC
[jira] Created: (CASSANDRA-1292) Multiple migrations might run at
once
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
Priority: Critical
Fix For: 0.7
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.
[jira] Commented: (CASSANDRA-1292) Multiple migrations might run at
once
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892925#action_12892925 ]
Gary Dusbabek commented on CASSANDRA-1292:
------------------------------------------
same thing goes for loadSchemaFromYaml()
> 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
>
>
> 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.
[jira] Assigned: (CASSANDRA-1292) Multiple migrations might run at
once
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-1292:
-----------------------------------------
Assignee: Gary Dusbabek
> 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
>
>
> 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.
[jira] Updated: (CASSANDRA-1292) Multiple migrations might run at
once
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-1292) Multiple migrations might run at
once
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893266#action_12893266 ]
Stu Hood commented on CASSANDRA-1292:
-------------------------------------
+1
> 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.
[jira] Commented: (CASSANDRA-1292) Multiple migrations might run at
once
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.