[
https://issues.apache.org/jira/browse/TEZ-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353365#comment-14353365
]
Hitesh Shah commented on TEZ-2179:
----------------------------------
Thanks for the clarification. In that case, we can probably remove the related
entities based on the answer by Zhijie on the question below.
[~zjshen] With ATS v2, will the related entities be useful for linking entities
and should we retain their use? Today, based on this jira, it seems that we
cannot make use of them in a secure environment.
> 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)
