[
https://issues.apache.org/jira/browse/CASSANDRA-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-3833.
---------------------------------------
Resolution: Later
> support arbitrary topology transitions
> ---------------------------------------
>
> Key: CASSANDRA-3833
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3833
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Peter Schuller
> Assignee: Peter Schuller
>
> Once we have the locator abstracted (with the gossiper being a
> particular concrete implementation), we want to change the locator
> abstraction to not express changes in ring topology on a per-node
> basis; rather we want to use an abstraction which communicates two
> arbitrary ring states; one state for the read set, and one for the
> write set.
> Once this abstraction is in place, the (pluggable) locator will be
> able to make bulk changes to a ring at once. Main points:
> * Must be careful in handling consistency level during ring
> transitions, such that a given node in the read set corresponds to a
> specific node in the write set. This will impose some restrictions
> on completion of transitions, to avoid code complexity, so it is an
> important point.
> * All code outside of gossip (and any other locator that works
> similarly) will be agnostic about individual changes to nodes, and
> will instead only be notified when new ring states are available (in
> aggregate). This makes the change non-trivial because all code that
> currently is oriented around individual node changes always
> producing a valid ring, will have to be changed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
