[jira] [Commented] (TEZ-3611) Create lightweight summary events for ATS.

["TezQA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEZ-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964226#comment-15964226 ] 

TezQA commented on TEZ-3611:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12862804/TEZ-3611.06.patch
  against master revision f355a05.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2370//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2370//console

This message is automatically generated.

> 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, TEZ-3611.06.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)