hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5981) Log levels of certain MR logs can be changed to DEBUG
Date Fri, 08 May 2015 17:07:02 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534943#comment-14534943
] 

Hudson commented on MAPREDUCE-5981:
-----------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #7776 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7776/])
MAPREDUCE-5981. Log levels of certain MR logs can be changed to DEBUG. (devaraj: rev dc2b2ae31f2eb6dae324c2e14ed7660ce605a89b)
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/Fetcher.java
* hadoop-mapreduce-project/CHANGES.txt
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/ShuffleSchedulerImpl.java


> Log levels of certain MR logs can be changed to DEBUG
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-5981
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5981
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 2.7.0
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>             Fix For: 2.8.0
>
>         Attachments: MAPREDUCE-5981.02.patch, MAPREDUCE-5981.patch
>
>
> Following map reduce logs can be changed to DEBUG log level as they appear too many times
in the log file and are not that important for debugging.
> 1. In org.apache.hadoop.mapreduce.task.reduce.Fetcher#copyFromHost(Fetcher.java : 313),
the second log is not required to be at info level. This can be moved to debug as a warn log
is anyways printed if verifyReply fails.
>       SecureShuffleUtils.verifyReply(replyHash, encHash, shuffleSecretKey);
>       LOG.info("for url="+msgToEncode+" sent hash and received reply");
> 2. Thread related info need not be printed in logs at INFO level. Below 2 logs can be
moved to DEBUG
>     a) In org.apache.hadoop.mapreduce.task.reduce.ShuffleSchedulerImpl#getHost(ShuffleSchedulerImpl.java
: 381), below log can be changed to DEBUG
>    LOG.info("Assigning " + host + " with " + host.getNumKnownMapOutputs() +
>                " to " + Thread.currentThread().getName());
>     b) In org.apache.hadoop.mapreduce.task.reduce.ShuffleScheduler.getMapsForHost(ShuffleSchedulerImpl.java
: 411), below log can be changed to DEBUG
>  LOG.info("assigned " + includedMaps + " of " + totalSize + " to " +
>              host + " to " + Thread.currentThread().getName());
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message