[
https://issues.apache.org/jira/browse/SOLR-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992776#comment-13992776
]
Noble Paul edited comment on SOLR-6027 at 5/8/14 2:11 PM:
----------------------------------------------------------
I still don't know how to write a test case for this
was (Author: noble.paul):
I still don't know ow to write a test case for this
> 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: [email protected]
For additional commands, e-mail: [email protected]
