[
https://issues.apache.org/jira/browse/MAPREDUCE-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524565#comment-14524565
]
Hadoop QA commented on MAPREDUCE-4308:
--------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12530811/mapreduce-4308-branch-1.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5497/console |
This message was 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
> 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)
