[
https://issues.apache.org/jira/browse/YARN-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-2770:
------------------------------
Attachment: YARN-2770.1.patch
Created a patch:
* Add two timeline client APIs - renew/cancel delegation token
* Make TimelineDelegationTokenIdentifier.Renewer extend TokenRenewer and
implement renew and cancel logic by using timeline client APIs
* Change YarnClientImpl to set the renewer of the timeline DT to the user of RM
daemon.
* Add the test cases to validate renew/cancel APIs
* Have done end-to-end test to verify that the automatic DT renew works in a
secure cluster.
> Timeline delegation tokens need to be automatically renewed by the RM
> ---------------------------------------------------------------------
>
> Key: YARN-2770
> URL: https://issues.apache.org/jira/browse/YARN-2770
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: 2.5.0
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Priority: Critical
> Attachments: YARN-2770.1.patch
>
>
> YarnClient will automatically grab a timeline DT for the application and pass
> it to the app AM. Now the timeline DT renew is still dummy. If an app is
> running for more than 24h (default DT expiry time), the app AM is no longer
> able to use the expired DT to communicate with the timeline server. Since RM
> will cache the credentials of each app, and renew the DTs for the running
> app. We should provider renew hooks similar to what HDFS DT has for RM, and
> set RM user as the renewer when grabbing the timeline DT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
