hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6082) Excessive logging by org.apache.hadoop.util.Progress when value is NaN
Date Thu, 11 Sep 2014 19:34:35 GMT

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

Jason Lowe commented on MAPREDUCE-6082:

+1 lgtm as well.  Commiting this.

> Excessive logging by org.apache.hadoop.util.Progress when value is NaN
> ----------------------------------------------------------------------
>                 Key: MAPREDUCE-6082
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6082
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Mit Desai
>            Assignee: Mit Desai
>         Attachments: MAPREDUCE-6082.patch
> MAPREDUCE-5671 fixed the "illegal" progress values that do not fall into (0,1) interval
when the progress value is given. Whenever illegal value was encountered, LOG.warn would log
that incident.
> As  a result, each of the task's syslog will be full of  WARN [main] org.apache.hadoop.util.Progress:
Illegal progress value found, progress is Float.NaN. Progress will be changed to 0
> Each input record will contribute to one line of such log, leading to most
> of the tasks' syslog > 1GB.
> We will need to change the log level to debug to avoid such excessive logging.

This message was sent by Atlassian JIRA

View raw message