cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3833) support arbitrary topology transitions
Date Sun, 12 Feb 2012 00:38:59 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Peter Schuller updated CASSANDRA-3833:
--------------------------------------

    Summary: support arbitrary topology transitions   (was: support locator support arbitrary
topology transitions )
    
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message