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 "Haibo Chen (JIRA)" <ji...@apache.org> on 2017/03/10 00:53:38 UTC

[jira] [Updated] (MAPREDUCE-6752) Bad logging practices in mapreduce

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

Haibo Chen updated MAPREDUCE-6752:
----------------------------------
    Labels: easyfix easytest newbie  (was: easyfix easytest)

> 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.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org