[
https://issues.apache.org/jira/browse/TEZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366103#comment-14366103
]
Jonathan Eagles commented on TEZ-2205:
--------------------------------------
[~hitesh], I think it is correct to say that there is currently a mismatch in
usage of this flag at least in secure environments. In a secure environment,
tez relies on the timeline server delegation token retrieved by the
YarnClientImp (yarn.timeline-service.enabled), in order to postEntities from
the AM. The client doesn't have this issue (it is able to retrieve its own
delegation token) while putting the domain unless the job was run from within
oozie (but that is another story).
So as I understand it, tez either needs to completely ignore
yarn.timeline-service.enabled and fetch its own timeline server delegation
token... or it needs to pay attention to this flag and fallback to simple
history when yarn.timeline-service.enabled=false. Seems like you are suggesting
the first case.
Jon
> 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
>
> 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)
