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 "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2010/05/07 07:19:48 UTC

[jira] Moved: (MAPREDUCE-1770) have option to limit stderr output from user scripts in hadoop streaming

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

Amareshwari Sriramadasu moved HADOOP-3984 to MAPREDUCE-1770:
------------------------------------------------------------

              Project: Hadoop Map/Reduce  (was: Hadoop Common)
                  Key: MAPREDUCE-1770  (was: HADOOP-3984)
    Affects Version/s:     (was: 0.17.2)

> have option to limit stderr output from user scripts in hadoop streaming
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1770
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1770
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Joydeep Sen Sarma
>
> People often echo to stderr to debug their programs.  We have had cases where someone inadvertently dumped large amounts of data to stderr. this created large userlog directories and caused quite a few mapred slaves to become dysfunctional (logs partition was full).
> Hence looking for a defensive measure against such errant scripts. We are currently putting in a limit on the number of bytes from the script's stderr that are forwarded to System.err.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.