Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Tue, 2 Feb 2016 03:45:39 +0000 (UTC)
From: "Bikas Saha (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12935794.1454370510000.272684.1454384739786@Atlassian.JIRA>
In-Reply-To: <JIRA.12935794.1454370510000@Atlassian.JIRA>
References: <JIRA.12935794.1454370510000@Atlassian.JIRA>
 <JIRA.12935794.1454370510364@arcas>
Subject: [jira] [Commented] (TEZ-3089) TaskConcurrencyAnalyzer can return
 negative task count with very large jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bikas Saha commented on TEZ-3089:
---------------------------------

If either event has type other than start or finish then +1 will be return. Is that desired or should that only be o1=finish and o2=start?

{code}+            if (o1.eventType.equals(EventType.START)
+                && o2.eventType.equals(EventType.FINISH)) {
+              return -1;
+            } else {
+              return 1;
+            }
{code}

> TaskConcurrencyAnalyzer can return negative task count with very large jobs
> ---------------------------------------------------------------------------
>
>                 Key: TEZ-3089
>                 URL: https://issues.apache.org/jira/browse/TEZ-3089
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>         Attachments: TEZ-3089.1.patch
>
>
> timeInfoset comparator should ideally include timestamp along with eventtype to work properly.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)