[ https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369607#comment-14369607 ]
Jonathan Eagles commented on YARN-2375: --------------------------------------- [~hitesh], I think the part that will help you gain understanding is that RM itself has a timeline client that it uses to renew the delegation tokens given at job submission time. If the RM has this flag off then all jobs submitted with a timeline service delegation token will fail to submit. If the RM has this flag on, then the timeline service integration is on for all clients a situation that has to be avoided considering the scale limitations and maturity of the timeline service. For Tez, possibly we can stop looking at the yarn.timeline-service.enabled and fetch our own delegation token? Another approach is to fallback to simple history when timeline-service is disabled. > 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 (v6.3.4#6332)