You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2016/11/15 08:58:59 UTC

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

     [ https://issues.apache.org/jira/browse/SOLR-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shalin Shekhar Mangar resolved SOLR-9736.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 6.4
                   master (7.0)

Thanks Dat!

> 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
>             Fix For: master (7.0), 6.4
>
>         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