[
https://issues.apache.org/jira/browse/TEZ-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873390#comment-15873390
]
Rohini Palaniswamy commented on TEZ-3611:
-----------------------------------------
bq. do you use counters on the main dag listing page
Do you mean the All DAGs page? Till now did not realize it was possible to
compare counters across DAGs in that page. If I had known would have used it
when comparing different runs of a script (Filtering on the DAG name). Possible
to keep that feature but turned off based on a config? I am fine it being
turned off by default. Would like to keep it turned on in our deployment. Many
users have data varying through the day for the hourly runs and many would be
find it useful to do quick comparison for the different hourly DAGs with those
counters.
> 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)
