cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-826) Implement a replication strategy for the KS that holds KS/CF defnitions.
Date Mon, 22 Mar 2010 20:43:27 GMT

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

Gary Dusbabek commented on CASSANDRA-826:
-----------------------------------------

That's one way of doing it, but the more I've thought about it and worked on it, I'm not sure
that replicating everywhere is the best approach.  I prefer using a pure gossip approach:
 NodeA has schema updated via thrift, makes local changes and then gossips it to all nodes.
 Those nodes realize they are on an older version and request all migrations between their
versions and the version that was gossiped.  The migrations are then applied.

The main advantage is that it is a one-size-fits all approach: it works for a live cluster,
it works for a bootstrapping node (re: your comment), it works for a node coming back into
the cluster.

It also avoids any synchronization issues involved with a mutation arriving after the version
is gossiped.



> Implement a replication strategy for the KS that holds KS/CF defnitions.
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-826
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-826
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>             Fix For: 0.7
>
>         Attachments: v2-0001-push-replicationFactor-into-a-getter.txt, v2-0002-everywhere-replication-strategy.txt
>
>
> Implement a replication strategy for the KS that holds KS/CF defnitions.
> It ignores replication factor and replicates to all nodes.

-- 
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