[
https://issues.apache.org/jira/browse/MAPREDUCE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053007#comment-14053007
]
Hadoop QA commented on MAPREDUCE-5954:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12654187/MAPREDUCE-5954.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The following test timeouts occurred in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:
org.apache.hadoop.mapred.pipes.TestPipeApplication
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4716//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4716//console
This message is automatically generated.
> 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
> Attachments: MAPREDUCE-5954.patch
>
>
> MRClientService#getTaskReports 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)
