hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6242) Progress report log is incredibly excessive in application master
Date Thu, 05 Feb 2015 19:34:35 GMT

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

Hadoop QA commented on MAPREDUCE-6242:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12696817/MAPREDUCE-6242.001.patch
  against trunk revision d27439f.

    {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:red}-1 eclipse:eclipse{color}.  The patch failed to build with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) 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-MAPREDUCE-Build/5163//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5163//console

This message is automatically generated.

> Progress report log is incredibly excessive in application master
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-6242
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6242
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster
>    Affects Versions: 2.4.0
>            Reporter: Jian Fang
>            Assignee: Varun Saxena
>         Attachments: MAPREDUCE-6242.001.patch
>
>
> We saw incredibly excessive logs in application master for a long running one with many
task attempts. The log write rate is around 1MB/sec in some cases. 
> Most of the log entries were from the progress report such as the following ones.
>     2015-02-03 17:46:14,321 INFO [IPC Server handler 56 on 37661] org.apache.hadoop.mapred.TaskAttemptListenerImpl:
Progress of TaskAttempt attempt_1422985365246_0001_m_000000_0 is : 0.15605757
>     2015-02-03 17:46:17,581 INFO [IPC Server handler 2 on 37661] org.apache.hadoop.mapred.TaskAttemptListenerImpl:
Progress of TaskAttempt attempt_1422985365246_0001_m_000000_0 is : 0.4108217
>     2015-02-03 17:46:20,426 INFO [IPC Server handler 0 on 37661] org.apache.hadoop.mapred.TaskAttemptListenerImpl:
Progress of TaskAttempt attempt_1422985365246_0001_m_000002_0 is : 0.06634143
>     2015-02-03 17:46:20,807 INFO [IPC Server handler 4 on 37661] org.apache.hadoop.mapred.TaskAttemptListenerImpl:
Progress of TaskAttempt attempt_1422985365246_0001_m_000000_0 is : 0.55556506
>     2015-02-03 17:46:21,013 INFO [IPC Server handler 6 on 37661] org.apache.hadoop.mapred.TaskAttemptListenerImpl:
Progress of TaskAttempt attempt_1422985365246_0001_m_000001_0 is : 0.21723115
> Looks like the report interval is controlled by a hard-coded variable PROGRESS_INTERVAL
as 3 seconds in class org.apache.hadoop.mapred.Task. We should allow users to set the appropriate
progress interval for their applications.



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

Mime
View raw message