[
https://issues.apache.org/jira/browse/KNOX-2736?focusedWorklogId=770699&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-770699
]
ASF GitHub Bot logged work on KNOX-2736:
----------------------------------------
Author: ASF GitHub Bot
Created on: 16/May/22 08:35
Start Date: 16/May/22 08:35
Worklog Time Spent: 10m
Work Description: zeroflag merged PR #568:
URL: https://github.com/apache/knox/pull/568
Issue Time Tracking
-------------------
Worklog Id: (was: 770699)
Time Spent: 40m (was: 0.5h)
> Knox clients should support retry/failover
> ------------------------------------------
>
> Key: KNOX-2736
> URL: https://issues.apache.org/jira/browse/KNOX-2736
> Project: Apache Knox
> Issue Type: Improvement
> Components: KnoxShell
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Not having retries in knox clients can cause service upgrade failures.
> The apache http client has a default mechanism
> (StandardHttpRequestRetryHandler and DefaultServiceUnavailableRetryStrategy)
> to support retries.
> * DefaultServiceUnavailableRetryStrategy only retries in case of a 503 -
> ServiceUnavailable.
> * StandardHttpRequestRetryHandler retries when a non excluded exception
> occurs during the request.
> The excluded exceptions are: InterruptedIOException, UnknownHostException,
> ConnectException, SSLException. In these cases no retry is going to happen.
> The following HTTP methods are considered idempotent so they can be retried:
> GET, HEAD, PUT, DELETE, OPTIONS, TRACE.
> Note that if an endpoint is implemented as a non-idempotent way (for example
> a PUT) then this might have unwanted side-effects.
> Other methods such as POST are only retried if the request has not yet
> written out to the output stream when the error happened. Or if
> requestSentRetryEnabled is enabled.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
