[
https://issues.apache.org/jira/browse/MAPREDUCE-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211535#comment-16211535
]
Guilherme Gribeler commented on MAPREDUCE-6752:
-----------------------------------------------
I also agree that the System.out.println calls could be replaced by LOG.debug
calls, as well as the LOG.info call. I can generate a patch for this issue if
this solution is ok. Can I do it from the most recent released version
(3.0.0-beta1) ?
> Bad logging practices in mapreduce
> ----------------------------------
>
> Key: MAPREDUCE-6752
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6752
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 2.7.2
> Reporter: Nemo Chen
> Labels: easyfix, easytest, newbie
>
> Similar to previous issue HADOOP-3029, in the file:
> hadoop-rel-release-2.7.2/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/speculate/DefaultSpeculator.java
> line 253, the whole method is for debugging purpose, therefore the log:
> {code:borderStyle=solid}
> LOG.info("We got asked to run a debug speculation scan.");
> {code}
> should be set to debug level instead of info level to avoid redundant
> information.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
