[
https://issues.apache.org/jira/browse/SOLR-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666549#comment-15666549
]
ASF subversion and git services commented on SOLR-9736:
-------------------------------------------------------
Commit eedc284c4d45bf26bca8b92e7a86a45b0c9e2330 in lucene-solr's branch
refs/heads/branch_6x from [~shalinmangar]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=eedc284 ]
SOLR-9736: Solr resolves the collection name against the first available leader
or first replica of the first slice
(cherry picked from commit 0d290ae)
> HttpSolrCall always prefer leader
> ---------------------------------
>
> Key: SOLR-9736
> URL: https://issues.apache.org/jira/browse/SOLR-9736
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-9736.patch, SOLR-9736.patch, SOLR-9736.patch,
> SOLR-9736.patch
>
>
> Currently, `HttpSolrCall.getCoreByCollection` always picks the first
> available leader ( or first replica ) of the first slice. It puts undue
> pressure on leaders and quite possibly on the wrong ones
--
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
