[
https://issues.apache.org/jira/browse/TEZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378536#comment-14378536
]
Hitesh Shah commented on TEZ-2205:
----------------------------------
[~lichangleo] In the end, someone has to check that config and make some
choices on how to act based on the configured value :). In an ideal world, the
yarn config would be checked and enforced by yarn libraries and not by yarn
applications. Also, [~lichangleo], based on [~rohini]'s comment, if YARN does
not have the hollow class, this would imply that there needs to have the hollow
implementation in Tez.
i.e option 3's impl would be:
- check yarn timeline enabled flag and make the revelant classes that use
ATS to be a no-op.
- Add a log.warn if ats is configured but yarn timeline is disabled.
[~zjshen] [~jeagles] comments on this?
It would be good to try and get a final consensus on whether we enforce the
yarn-specific flag in YARN or in the Application. Based on this, we can unblock
[~lichangleo] to be able to make the changes.
> Tez still tries to post to ATS when yarn.timeline-service.enabled=false
> -----------------------------------------------------------------------
>
> Key: TEZ-2205
> URL: https://issues.apache.org/jira/browse/TEZ-2205
> Project: Apache Tez
> Issue Type: Sub-task
> Affects Versions: 0.6.1
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: TEZ-2205.wip.patch
>
>
> when set yarn.timeline-service.enabled=false, Tez still tries posting to ATS,
> but hits error as token is not found. Does not fail the job because of the
> fix to not fail job when there is error posting to ATS. But it should not be
> trying to post to ATS in the first place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
