[
https://issues.apache.org/jira/browse/SOLR-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-9736:
----------------------------------------
Attachment: SOLR-9736.patch
This helps reduce load on leader cores but doesn't solve the real problem which
is that we might still send the request to the wrong leader. But this is a good
first step.
I updated the patch to add basic javadocs on the new methods in DocCollection
as well as on the new RandomIterator class.
> 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
>
>
> 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
