[jira] [Comment Edited] (SOLR-9736) HttpSolrCall always prefer leader

["Cao Manh Dat (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665726#comment-15665726 ] 

Cao Manh Dat edited comment on SOLR-9736 at 11/15/16 2:04 AM:
--------------------------------------------------------------

[~shalinmangar] Thank you for review my patch, because the cores are chosen randomly so we can miss some core is chosen in the test.

Updated patch, in this patch I modified the test to run more request, to make sure that all the 
cores are chosen ( I ran the test about 300 times and it still passed )


was (Author: caomanhdat):
Updated patch, in this patch I modified the test to run more request, to make sure that all the cores are chosen.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org