[
https://issues.apache.org/jira/browse/TEZ-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harish Jaiprakash updated TEZ-3611:
-----------------------------------
Attachment: TEZ-3611.01.patch
Created TEZ_DAG_PLAN entity and split the DAGSubmittedEvent to be sent as two
entities, TEZ_DAG_ID which contains existing data without dagPlan and
TEZ_DAG_PLAN which contains only the dagPlan.
This change is only made for ATSv15, since ATSv1 does not have concept of
summary events. Should I make it consistent for both?
Leaving the counters as suggested by [~sseth] to ensure the UI can display them
in the "All Dags" page.
> 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
>
>
> 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)
