Return-Path: X-Original-To: apmail-tez-issues-archive@minotaur.apache.org Delivered-To: apmail-tez-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 391611864E for ; Mon, 27 Jul 2015 18:54:05 +0000 (UTC) Received: (qmail 44734 invoked by uid 500); 27 Jul 2015 18:54:04 -0000 Delivered-To: apmail-tez-issues-archive@tez.apache.org Received: (qmail 44676 invoked by uid 500); 27 Jul 2015 18:54:04 -0000 Mailing-List: contact issues-help@tez.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tez.apache.org Delivered-To: mailing list issues@tez.apache.org Received: (qmail 44666 invoked by uid 99); 27 Jul 2015 18:54:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jul 2015 18:54:04 +0000 Date: Mon, 27 Jul 2015 18:54:04 +0000 (UTC) From: "Bikas Saha (JIRA)" To: issues@tez.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (TEZ-2612) Critical path analyzer for DAGs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TEZ-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha reassigned TEZ-2612: ------------------------------- Assignee: Bikas Saha > Critical path analyzer for DAGs > ------------------------------- > > Key: TEZ-2612 > URL: https://issues.apache.org/jira/browse/TEZ-2612 > Project: Apache Tez > Issue Type: Bug > Reporter: Rajesh Balamohan > Assignee: Bikas Saha > > This analyzer plugin/tool can be used to understand the important vertices/tasks of interest in large DAG for perf analysis / finding bottlenecks. It can be used to find out 1.input dependency, 2. failure dependency, 3. scheduling dependency (may be at later stage). > Creating this as a uber ticket. Getting this detail at vertex level might be possible with the existing logs derived from ATS. For task level analysis, certain more details are required. > 1. Timeline details like when fetch/merge/compute/sort etc are not captured now. These details can possibly be added in TaskCompletionEvent > 2. Need additional details like the last event that completed processing in the input (for tracing at task level) > 3. Add downstream task attempt that caused the higher level task to get rescheduled/restarted. This can be used in terms of understanding in cases where the task failed due to read-error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)