Hitesh Shah commented on YARN-2375:

[~jeagles] Was the original intention to have this flag be used on a per job 
basis? If that is the case, the original code ( assuming both the YarnClient 
and TimelineClient) handled the flag and treated all calls as no-op if the flag 
was set to false should work correct? 

If not, we would need to either an additional flag to Tez to handle 
enabling/disabling ATS even though the history logger configured is the ATS 
logger or somehow rely on the Yarn config.

> 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
>             Fix For: 2.7.0
>         Attachments: YARN-2375.1.patch, YARN-2375.patch, YARN-2375.patch, 
> YARN-2375.patch, YARN-2375.patch
> 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

Reply via email to