[
https://issues.apache.org/jira/browse/TEZ-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353684#comment-14353684
]
Zhijie Shen commented on TEZ-2179:
----------------------------------
Sorry, I go back to check the specification of the timeline domain again.
Currently, in a secure mode, the entity are not allowed to be related to the
entity in the other domain. Currently, YARN framework entities are put into the
DEFAULT domain, such that TEZ entities cannot relate to. It's not a bug, but
kind of the constraint.
To work around the constraint, Tez could logically connect the Tez entity and
YARN framework entity in the other way. For example, we can add
"appId:appid_xxxx_yyyy" into the otherinfo section.
> Timeline relatedentries missing cause exaggerated warning
> ---------------------------------------------------------
>
> Key: TEZ-2179
> URL: https://issues.apache.org/jira/browse/TEZ-2179
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.6.1
> Reporter: Chang Li
>
> Have run into an issue where TimelineClient has posted entities in the
> timeline event posted. The related entry is not found (i believe because I
> didn't have generic history turned on) and Yarn timeline server assumes the
> missing event belongs to the default domain. Regular users don't have
> permissions to the default domain and so the update to the related entity
> fails. The posting of the event succeeds, just that the cross-link related
> entity is not updated. However in the log I see the warning which is going to
> scare users
> {code}
> 2015-02-24 20:01:24,526 WARN [HistoryEventHandlingThread]
> ats.ATSHistoryLoggingService: Could not post history event to ATS,
> atsPutError=6, entityId=tez_application_1423769157162_273679,
> eventType=APP_LAUNCHED
> 2015-02-24 20:01:24,526 WARN [HistoryEventHandlingThread]
> ats.ATSHistoryLoggingService: Could not post history event to ATS,
> atsPutError=6, entityId=tez_appattempt_1423769157162_273679_000001,
> eventType=AM_LAUNCHED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
