[
https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212928#comment-14212928
]
Zhijie Shen commented on YARN-2375:
-----------------------------------
bq. While running secure timeline server with ats flag set to disabled on
resource manager, Timeline delegation token renewer throws an NPE.
This is a bug. DT related API methods doesn't check if isEnabled == true. On
the other side, the internal stuff is only inited when isEnabled == true. This
is why NPE happens. Will file a separate Jira for it.
As to removing the global flag, I'm not sure if we should do that. Nowadays, we
still don't assume the timeline server is always up as other components in a
YARN cluster: RM and NM. Then, if the timeline server is not setup but the YARN
cluster assumes it is up, it will result in problems. For example, app
submission fails at getting the timeline DT in a secure cluster.
Therefore, this config should be kept to serve as the flag to indicate if we
have setup the timeline server for the YARN cluster, until we promote it the be
the always on daemon like RM and NM. Thoughts?
> Allow enabling/disabling timeline server per framework
> ------------------------------------------------------
>
> Key: YARN-2375
> URL: https://issues.apache.org/jira/browse/YARN-2375
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Mit Desai
>
> This JIRA is to remove the ats enabled flag check within the
> TimelineClientImpl. Example where this fails is below.
> While running secure timeline server with ats flag set to disabled on
> resource manager, Timeline delegation token renewer throws an NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
