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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:33:22 UTC
[jira] [Updated] (MAPREDUCE-4308) Remove excessive split log
messages
[ https://issues.apache.org/jira/browse/MAPREDUCE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated MAPREDUCE-4308:
----------------------------------------
Labels: BB2015-05-TBR (was: )
> 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
> Labels: BB2015-05-TBR
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)