[
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.05.patch
Fixed ATSImportTool to be compatible with earlier and current logging formats.
[~rajesh.balamohan] Please tell me if the fix is fine. Currently I have taken
the approach of merging the data from TEZ_DAG_EXTRA_INFO into the "dag" json.
Another approach is to add TEZ_DAG_EXTRA_INFO as another file in the zip and
then change the processing in ATSFileParser/BaseParser to handle this case.
> 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,
> TEZ-3611.04.patch, TEZ-3611.05.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)
