You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Mit Desai (JIRA)" <ji...@apache.org> on 2014/09/11 22:02:34 UTC

[jira] [Commented] (HADOOP-11085) Excessive logging by org.apache.hadoop.util.Progress when value is NaN

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

Mit Desai commented on HADOOP-11085:
------------------------------------

Thanks Jason.

> Excessive logging by org.apache.hadoop.util.Progress when value is NaN
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-11085
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11085
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Mit Desai
>            Assignee: Mit Desai
>             Fix For: 2.6.0
>
>         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
(v6.3.4#6332)