You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2011/06/13 14:34:51 UTC

[jira] [Commented] (CASSANDRA-2715) simplify schema reconciliation

    [ https://issues.apache.org/jira/browse/CASSANDRA-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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