[jira] [Commented] (CASSANDRA-2715) simplify schema reconciliation
[ https://issues.apache.org/jira/browse/CASSANDRA-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13048537#comment-13048537 ] Gary Dusbabek commented on CASSANDRA-2715: -- +1 simplify schema reconciliation -- Key: CASSANDRA-2715 URL: https://issues.apache.org/jira/browse/CASSANDRA-2715 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 0.7.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.8.1 Attachments: 2715.txt, 2715.txt Currently, schema migrations can be replayed from one node to another in any of three ways: - a node processes a migration from a client, and pushes it to all live nodes (Migration.announce on the source) - a node sees that another node's schema version is older than his (MigrationManager.onChange on the source) - a node sees that his own schema version is older than another's and makes an explicit request (MigrationManager.onChange on the target, DefinitionsAnnounceVerbHandler on the source) The last of these is an optimization that isn't worth the extra complexity -- under normal conditions, the initial announce from the coordinator updates everyone, and in recovery situations the latency gain of #3 over #2 is only a few seconds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2715) simplify schema reconciliation
[ https://issues.apache.org/jira/browse/CASSANDRA-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13048593#comment-13048593 ] Hudson commented on CASSANDRA-2715: --- Integrated in Cassandra-0.8 #166 (See [https://builds.apache.org/job/Cassandra-0.8/166/]) remove active-pull schemarequests patch by jbellis; reviewed by jbellis for CASSANDRA-2715 jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1135116 Files : * /cassandra/branches/cassandra-0.8/CHANGES.txt * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/DropColumnFamily.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/RenameColumnFamily.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/DataTracker.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/DropKeyspace.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/Migration.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/RenameKeyspace.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/UpdateColumnFamily.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/MigrationManager.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/AddColumnFamily.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/DefinitionsUpdateVerbHandler.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/DefinitionsAnnounceVerbHandler.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/migration/AddKeyspace.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/db/DefinitionsUpdateResponseVerbHandler.java * /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/StorageService.java simplify schema reconciliation -- Key: CASSANDRA-2715 URL: https://issues.apache.org/jira/browse/CASSANDRA-2715 Project: Cassandra Issue Type: Improvement Components: Core Affects Versions: 0.7.0 Reporter: Jonathan Ellis Assignee: Jonathan Ellis Priority: Minor Fix For: 0.8.1 Attachments: 2715.txt, 2715.txt Currently, schema migrations can be replayed from one node to another in any of three ways: - a node processes a migration from a client, and pushes it to all live nodes (Migration.announce on the source) - a node sees that another node's schema version is older than his (MigrationManager.onChange on the source) - a node sees that his own schema version is older than another's and makes an explicit request (MigrationManager.onChange on the target, DefinitionsAnnounceVerbHandler on the source) The last of these is an optimization that isn't worth the extra complexity -- under normal conditions, the initial announce from the coordinator updates everyone, and in recovery situations the latency gain of #3 over #2 is only a few seconds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
