[
https://issues.apache.org/jira/browse/TEZ-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899973#comment-15899973
]
Siddharth Seth commented on TEZ-3611:
-------------------------------------
bq. I'll make the change to return a list of event instead of a single event
and remove special handling of summary events. I made the changes to keep
HistoryEventTimelineConversion's API backwards compatible. Might not be a
requirement, please do confirm.
Is there a reason to make it compatible? It's not marked prIvate / public.
bq. The convertToTimelineEntity with false is being invoked by
ATSHistoryLoggingService. I can make the same changes there and keep both
loggers consisted w.r.t data format for ATS.
Sounds good. Wonder if we should get rid of ATSHistoryLoggingService at some
point.
> Create lightweight summary events for ATS.
> ------------------------------------------
>
> Key: TEZ-3611
> URL: https://issues.apache.org/jira/browse/TEZ-3611
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Harish Jaiprakash
> Assignee: Harish Jaiprakash
> Attachments: TEZ-3611.01.patch, TEZ-3611.02.patch, TEZ-3611.03.patch
>
>
> All DAG*Event are summary logs. DAGSubmittedEvent has dagPlan in it and
> DAGFinishedEvent has counters in it. And hence these events very large, which
> makes the dag landing page on the tez-ui very expensive.
> Split these events into two parts:
> * One which contains only data used by the tez-ui "All Dags" page which will
> go into summary log.
> * Another which will contain the current object, which will be part of the
> appropriate TimelineEntityGroupId.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
