Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 590B9117F8 for ; Wed, 2 Jul 2014 00:15:27 +0000 (UTC) Received: (qmail 88298 invoked by uid 500); 2 Jul 2014 00:15:26 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 88144 invoked by uid 500); 2 Jul 2014 00:15:26 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 87900 invoked by uid 99); 2 Jul 2014 00:15:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2014 00:15:25 +0000 Date: Wed, 2 Jul 2014 00:15:25 +0000 (UTC) From: "Maysam Yabandeh (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (MAPREDUCE-5954) Optional exclusion of counters from getTaskReports MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Maysam Yabandeh created MAPREDUCE-5954: ------------------------------------------ Summary: Optional exclusion of counters from getTaskReports Key: MAPREDUCE-5954 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5954 Project: Hadoop Map/Reduce Issue Type: Improvement Reporter: Maysam Yabandeh Assignee: Maysam Yabandeh MRClientService.getTaskReport returns the set of map or reduce tasks along with their counters, which are quite large. For big jobs, the response could be as large as 0.5 GB. This has a negative impact both on MRAppMaster and the monitoring tool that invokes getTaskReports. This problem has led Pig users to entirely disable getTaskReports for big jobs: https://issues.apache.org/jira/browse/PIG-4043 Many monitoring tools, including ours, do not need the task counters when invoking getTaskReports. Pig also does not make any use of task counters. Here are the usages of Tasks in pig: {code} protected void getErrorMessages(TaskReport reports[], String type, String msgs[] = reports[i].getDiagnostics(); if (HadoopShims.isJobFailed(reports[i])) { {code} and {code} protected long computeTimeSpent(TaskReport[] taskReports) { long timeSpent = 0; for (TaskReport r : taskReports) { timeSpent += (r.getFinishTime() - r.getStartTime()); } return timeSpent; } {code} GetTaskReportsRequest can be augmented with an optional boolean with which the monitoring tool can request excluding the counters form the response. This minor change is very simple and yet makes many existing monitoring tools more efficient. -- This message was sent by Atlassian JIRA (v6.2#6252)