You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/26 01:00:36 UTC
[jira] [Commented] (SOLR-5503) Retry 'forward to leader' requests
less aggressively - rather than on IOException, ConnectException.
[ https://issues.apache.org/jira/browse/SOLR-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832090#comment-13832090 ]
ASF subversion and git services commented on SOLR-5503:
-------------------------------------------------------
Commit 1545464 from [~markrmiller@gmail.com] in branch 'dev/trunk'
[ https://svn.apache.org/r1545464 ]
SOLR-5503: Retry 'forward to leader' requests less aggressively - rather than on IOException, ConnectException.
> Retry 'forward to leader' requests less aggressively - rather than on IOException, ConnectException.
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-5503
> URL: https://issues.apache.org/jira/browse/SOLR-5503
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 5.0, 4.7
>
>
> Most, we want to retry when a leader is not available - error 500 and IOExceptions are not as desirable for retries. We don't know if the request was successful or failed. Best to let the outside client get the error and deal with this.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org