[
https://issues.apache.org/jira/browse/TEZ-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349487#comment-14349487
]
Hitesh Shah edited comment on TEZ-2179 at 3/5/15 9:27 PM:
----------------------------------------------------------
[~lichangleo] Does the actual entity not get created at all? Or does only the
relationship aspect fail?
As long as the actual entity gets created properly, this might not be too much
of an issue unless the UI needs this data. We can switch to using otherInfo
instead of related entities if the question addressed to Zhijie cannot be
addressed cleanly.
[~zjshen] How does an application go about creating a relationship between an
application specific entity and an entity created by the YARN framework?
[~pramachandran] [~Sreenath] Do we use any yarn relationship entity info at all
in the UI or do we just rely on the tez entities?
was (Author: hitesh):
[~lichangleo] Does the actual entity not get created at all? Or does only the
relationship aspect fail?
[~zjshen] How does an application go about creating a relationship between an
application specific entity and an entity created by the YARN framework?
[~pramachandran] [~Sreenath] Do we use any yarn relationship entity info at all
in the UI or do we just rely on the tez entities?
> 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)
