[
https://issues.apache.org/jira/browse/SOLR-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-7493:
----------------------------------------
Attachment: SOLR-7493.patch
* Uses a random seeded with tests.seed of System.currentTimeMillis for shuffling
* Added a simple test which creates creates 3 jettys, 2 collections A, B such
that A has replicas on node1, node2 and collection B has replica on node3. The
test fires 10 search requests to node3 intended for collection A and asserts
that all requests do not go to the same replica of collection A.
> Requests aren't distributed evenly if the collection isn't present locally
> --------------------------------------------------------------------------
>
> Key: SOLR-7493
> URL: https://issues.apache.org/jira/browse/SOLR-7493
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.0
> Reporter: Jeff Wartes
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-7493.patch, SOLR-7493.patch
>
>
> I had a SolrCloud cluster where every node is behind a simple round-robin
> load balancer.
> This cluster had two collections (A, B), and the slices of each were
> partitioned such that one collection (A) used two thirds of the nodes, and
> the other collection (B) used the remaining third of the nodes.
> I observed that every request for collection B that the load balancer sent to
> a node with (only) slices for collection A got proxied to one *specific* node
> hosting a slice for collection B. This node started running pretty hot, for
> obvious reasons.
> This meant that one specific node was handling the fan-out for slightly more
> than two-thirds of the requests against collection B.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
