cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Overton (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-4123) vnodes aware Replication Strategy
Date Thu, 05 Apr 2012 13:59:24 GMT
vnodes aware Replication Strategy 

                 Key: CASSANDRA-4123
             Project: Cassandra
          Issue Type: Sub-task
            Reporter: Sam Overton
            Assignee: Sam Overton

The simplest implementation for this would be if NTS regarded a single host as a distinct
rack. This would prevent replicas being placed on the same host. The rest of the logic for
replica selection would be identical to NTS (but this would be removing a level of topology
hierarchy). This would be achievable just by writing a snitch to place hosts in their own

A better solution would be to add an extra level of hierarchy to NTS so that it still supported
DC & rack, and IP would be the new level at the bottom of the hierarchy. The logic would
remain largely the same.

I would very much like to build in Peter Schuller's notion of Distribution Factor (as described
in This requires a method
of defining a "replica set" for each host and then treating it in a similar way to a DC (ie.
RF replicas are chosen from that set, instead of from the whole cluster). 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message