hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4308) Remove excessive split log messages
Date Mon, 04 Jun 2012 16:51:23 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kihwal Lee updated MAPREDUCE-4308:
----------------------------------

    Attachment: mapreduce-4308-branch-1.patch
    
> 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

        

Mime
View raw message