You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2015/08/03 20:28:04 UTC

[jira] [Commented] (SOLR-7860) Standardize use of HttpSolrClients in Solr

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

Noble Paul commented on SOLR-7860:
----------------------------------

First of all , we must not dealing with http clients directly. There should be standard ways to do common operations

something like 
{code}
remoteCall("collection", "shardName", ANY|LEADER|NON-LEADER , params, payload)
remoteCall("collection", "shardName", replicaName, params, payload)
{code}

The call could be synchronous or asynchronous

> Standardize use of HttpSolrClients in Solr
> ------------------------------------------
>
>                 Key: SOLR-7860
>                 URL: https://issues.apache.org/jira/browse/SOLR-7860
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ramkumar Aiyengar
>            Priority: Minor
>         Attachments: SOLR-7860.patch
>
>
> {{HttpShardHandlerFactory}} and {{UpdateShardHandler}} already provide two places where one can get {{HttpSolrClient}}s with timeouts set up properly etc., but there are lots of miscellaneous places which instantiate their own, with hardcoded timeouts. These are just waiting for some environment to realize the timeouts are not suitable, and not configurable as well. We should standardize this (anyone knows why there two to begin with?), ideally this hardcoding shouldn't exist at all..



--
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