[jira] [Commented] (SOLR-6027) Replica assignments should try to take the host name into account so all replicas don't end up on the same host

["Mark Miller (JIRA)" <ji...@apache.org>]

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

Mark Miller commented on SOLR-6027:
-----------------------------------

I've got some stuff that should be reusable / useful here as part of my replica failover work - it has some simple code to create a specific cluster state using some mock objects. You setup various states and check that the nodes chosen match what you expect or doesn't violate what you don't expect when passed to a method that returns which nodes where chosen to create on. 

A state is created via a short string ie csrsrrcr*r, so it ende up being simple and fast to test the hall out of this types of thing, and then you need less variation in any integration tests. 

> Replica assignments should try to take the host name into account so all replicas don't end up on the same host
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-6027
>                 URL: https://issues.apache.org/jira/browse/SOLR-6027
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Timothy Potter
>            Priority: Minor
>         Attachments: SOLR-6027.patch
>
>
> I have 18 SolrCloud nodes distributed across 3 Ec2 instances, so 6 per instance. One of my collections was created with all replicas landing on different SolrCloud nodes on the same instance. Ideally, SolrCloud would be a little smarter and ensure that at least one of the replicas was on one of the other hosts.
> shard4: {
> 	http://ec2-??-??-??-239.compute-1.amazonaws.com:8988/solr/med_collection_shard4_replica1/ LEADER
> 	http://ec2-??-??-??-239.compute-1.amazonaws.com:8984/solr/med_collection_shard4_replica3/ 
> 	http://ec2-??-??-??-239.compute-1.amazonaws.com:8985/solr/med_collection_shard4_replica2/ 
> }
> I marked this as minor for now as it could be argued that I shouldn't be running that many Solr nodes per instance, but I'm seeing plenty of installs that are using higher-end instance types / server hardware and then running multiple Solr nodes per host.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org