You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/06/04 19:05:23 UTC
[jira] [Commented] (MAPREDUCE-4308) Remove excessive split log
messages
[ https://issues.apache.org/jira/browse/MAPREDUCE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288681#comment-13288681 ]
Hadoop QA commented on MAPREDUCE-4308:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12530811/mapreduce-4308-branch-1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2435//console
This message is automatically generated.
> Remove excessive split log messages
> -----------------------------------
>
> Key: MAPREDUCE-4308
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4308
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Affects Versions: 1.0.3
> Reporter: Kihwal Lee
> Fix For: 1.1.0
>
> Attachments: mapreduce-4308-branch-1.patch
>
>
> Job tracker currently prints out information on every split.
> {noformat}
> 2012-05-20 00:06:01,985 INFO org.apache.hadoop.mapred.JobInProgress:
> tip:task_201205100740_1745_m_000000 has split on node:/192.168.0.1
> /my.totally.madeup.host.com
> {noformat}
> I looked at one cluster and these messages were taking up more than 30% of the JT log. If jobs have large number of maps, it can be worse. I think it is reasonable to lower the log level of the statement from INFO to DEBUG.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira