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

Zhijie Shen commented on YARN-2779:
-----------------------------------

[~vinodkv], in the current code base, we're SystemMetricsPublisher to grab a 
timeline DT to talk to the timeline server in secure mode. That's why we need 
this Jira to add renew and cancel work.

But thinking of this issue again, it should be okay to let RM talk to the 
timeline server with kerberos directly. As this is the only process, which will 
not add too much workload to the kerberos server. So on the other hand, let's 
remove the getting DT logic, and let RM uses kerberos directly.

> SystemMetricsPublisher needs to renew and cancel timeline DT too
> ----------------------------------------------------------------
>
>                 Key: YARN-2779
>                 URL: https://issues.apache.org/jira/browse/YARN-2779
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, timelineserver
>    Affects Versions: 2.6.0
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>            Priority: Critical
>
> SystemMetricsPublisher is going to grab a timeline DT in secure mode as well. 
> The timeline DT will expiry after 24h. No DT renewer will handle renewing 
> work for SystemMetricsPublisher, but this has to been handled by itself. In 
> addition, SystemMetricsPublisher should cancel the timeline DT when it is 
> stopped, too.



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

Reply via email to