[
https://issues.apache.org/jira/browse/YARN-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899889#comment-15899889
]
Haibo Chen edited comment on YARN-3471 at 3/7/17 6:24 PM:
----------------------------------------------------------
Both 1) and 2) have been resolved after YARN-4675.
(TimelineClientConnectionRetry is called in a Jersey client filter that only
retries requests upon connection-related exceptions) Closing this. Feel free to
reopen it if you disagree.
was (Author: haibochen):
Both 1) and 2) have been resolved after YARN-4675.
(TimelineClientConnectionRetry is called in a Jersey client filter that only
retries requests upon connection-related exceptions) Closing this.
> Fix timeline client retry
> -------------------------
>
> Key: YARN-3471
> URL: https://issues.apache.org/jira/browse/YARN-3471
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: 2.8.0
> Reporter: Zhijie Shen
> Assignee: Haibo Chen
> Labels: YARN-5355
> Attachments: YARN-3471.1.patch, YARN-3471.2.patch
>
>
> I found that the client retry has some problems:
> 1. The new put methods will retry on all exception, but they should only do
> it upon ConnectException.
> 2. We can reuse TimelineClientConnectionRetry to simplify the retry logic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
