[
https://issues.apache.org/jira/browse/SOLR-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580551#comment-14580551
]
ASF subversion and git services commented on SOLR-7493:
-------------------------------------------------------
Commit 1684675 from sha...@apache.org in branch 'dev/branches/lucene_solr_5_2'
[ https://svn.apache.org/r1684675 ]
SOLR-7493: Fix compile issue after backport
> 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
> Fix For: 5.2.1, 5.3, Trunk
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
