[
https://issues.apache.org/jira/browse/MAPREDUCE-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048685#comment-18048685
]
ASF GitHub Bot commented on MAPREDUCE-6752:
-------------------------------------------
github-actions[bot] closed pull request #285: MAPREDUCE-6752: Bad logging
practices in mapreduce
URL: https://github.com/apache/hadoop/pull/285
> 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
> Priority: Major
> Labels: easyfix, easytest, newbie, pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]