lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-2466) CommonsHttpSolrServer will retry a query even if _maxRetries is 0
Date Tue, 12 Apr 2011 20:50:05 GMT


Hoss Man commented on SOLR-2466:

I haven't checked hte code but if i remember correctly (from another project) HttpClient and
it's RetryHandler "hook" are only used when dealing with *network* failures -- ie: connection
refused, connection timeout, connection aborted.  If a request is a success at the TCP layer,
but a failure at the HTTP layer (ie: 500) then you need your own retry logic external to the

that may be what SolrJ is doing, to account for transient errors (ie: trying to add during
a blocking commit or something like that)

> CommonsHttpSolrServer will retry a query even if _maxRetries is 0
> -----------------------------------------------------------------
>                 Key: SOLR-2466
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 1.4.1, 3.1, 4.0
>            Reporter: Tomás Fernández Löbbe
> The HttpClient library used by CommonsHttpSolrServer will retry by default 3 times a
request that failed on the server side, even if the _maxRetries field of  CommonsHttpSolrServer
is set to 0.
> The retry count should be managed in just one place and CommonsHttpSolrServer seems to
be the right one. 
> CommonsHttpSolrServer should override that HttpClient default to 0 retries, and manage
the retry count with the value of the field _maxRetries.

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message