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

Jonathan Ellis commented on CASSANDRA-5283:
-------------------------------------------

I don't understand what you are proposing.  How can it be both compatible with 
the existing strategy, and yet generate different replica assignments?
                
> giving SimpleStrategy rack alignment
> ------------------------------------
>
>                 Key: CASSANDRA-5283
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5283
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Dominique De Vito
>            Priority: Minor
>
> SimpleStrategy is not rack aware.
> But NetworkTopologyStrategy could lead to overloaded nodes, see 
> https://issues.apache.org/jira/browse/CASSANDRA-3810
> The idea here is to enable to use SimpleStrategy with the configuration 
> associated with NetworkTopologyStrategy:
> * the placement strategy would be the one of SimpleStrategy;
> * Cassandra would be able to exploit rack config (similar to the one of 
> NetworkTopologyStrategy) to give a simple placement diagnostic; such a 
> diagnostic could tell, for example:
> ** "optimal": if all replica are on different racks
> ** "sub-optimal": if some replica are on the same rack, while there are 
> replica on different racks
> ** "spof": if all replica are on the same rack
> ** "?": if the snitch doesn't provide enough information to make a diagnostic
> This enhancement of SimpleStrategy has multiple advantages:
> * it's compatible with (already existing) SimpleStrategy;
> * it sits between current SimpleStrategy and NetworkTopologyStrategy, so it's 
> helpful when expecting to move, for example, from 1 DC to 2 DC.
> * and more importantly, it's inline with Cassandra global strategy: offering 
> simple services, and providing tools to repair/fix the database.

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

Reply via email to