Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5981

Log levels of certain MR logs can be changed to DEBUG

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.7.0
    • 2.8.0, 3.0.0-alpha1
    • None
    • None
    • Reviewed

    Description

      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());

      Attachments

        1. MAPREDUCE-5981.02.patch
          3 kB
          Varun Saxena
        2. MAPREDUCE-5981.patch
          2 kB
          Varun Saxena

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            varun_saxena Varun Saxena
            varun_saxena Varun Saxena
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment