lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-12314) ConcurrentUpdateSolrClient doesn't respect the timeout's defined in the solr.xml file
Date Sat, 05 May 2018 02:30:00 GMT


Mark Miller commented on SOLR-12314:

We can't just remove it though. The CUSC timeout setters still need to work until they are

They also need to work if set one or both of them - if neither are set, we can just skip the
request config object, if both are set, we use it, and if one is set we have to get the right
default for the other to set on the request config.

I think this also breaks the time outs coming from the builder if set that way.

If you set timeouts on the client itself, they should work - it should only come from elsewhere
or a passed in HttpClient object if they are not explicitly set on the client itself.

> ConcurrentUpdateSolrClient doesn't respect the timeout's defined in the solr.xml file
> -------------------------------------------------------------------------------------
>                 Key: SOLR-12314
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>            Assignee: Varun Thacker
>            Priority: Major
>         Attachments: SOLR-12314.patch
> In ConcurrentUpdateSolrClient we create an HttpPost Request which allows you to set a
request config. If the request config is not provided httpclient will use the default request
> {code:java}
> org.apache.http.client.config.RequestConfig.Builder requestConfigBuilder = HttpClientUtil.createDefaultRequestConfigBuilder();
> if (soTimeout != null) {
>   requestConfigBuilder.setSocketTimeout(soTimeout);
> }
> if (connectionTimeout != null) {
>   requestConfigBuilder.setConnectTimeout(connectionTimeout);
> }
> method.setConfig(;{code}
> While creating the httpclient object we ensure that the default request is set with the
properties we care about.  This happens in HttpClientUtils#setupBuilder
> {code:java}
> RequestConfig requestConfig =;
> HttpClientBuilder retBuilder = builder.setDefaultRequestConfig(requestConfig);{code}
> So there is no need to set a per request config 
> Here is where the httpclient picks the request config is provided on the request itself
: []
> And if it's not provided it uses the default here :

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message