[ 
https://issues.apache.org/jira/browse/YARN-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171717#comment-14171717
 ] 

Li Lu commented on YARN-2673:
-----------------------------

After checking through the code, I'm planning to separate this into two steps. 
In the first step, we may want to add retry mechanisms to the jersey client 
that posts timeline entities and domains. After this step, timeline clients for 
non-secured clusters will be able to retry when timeline server is down. Then, 
on top of this, we can add retry mechanism to delegation token calls for 
secured clusters. I'll focus on the non-secured part in this Jira. All secured 
cluster/token related retry mechanisms will be uploaded to a separate Jira. 

> Add retry for timeline client
> -----------------------------
>
>                 Key: YARN-2673
>                 URL: https://issues.apache.org/jira/browse/YARN-2673
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Li Lu
>            Assignee: Li Lu
>
> Timeline client now does not handle the case gracefully when the server is 
> down. Jobs from distributed shell may fail due to ATS restart. We may need to 
> add some retry mechanisms to the client. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to