hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6220) Provide option to forbid stdout of MapReduce task
Date Fri, 10 Apr 2015 17:53:14 GMT

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

Ravi Prakash commented on MAPREDUCE-6220:
-----------------------------------------

Thanks YangHao. I see. I'm leaning towards providing this option now. This will probably be
a disincentive for fixing the original problem (too much verbosity) and performance will probably
be bad (those strings that you are redirecting to /dev/null need to be generated and perhaps
GCd afterwards). Trust me, you want to go and chase down those users anyway. However I sympathize
with the operation teams having to manage these badly behaving users.
1. Could you please rename TASK_LOG_STANDOUT_FORBID -> TASK_LOG_STDOUT_TO_DEVNULL
2.  (and task.container.log.standout.forbid -> task.container.log.stdout.to.devnull)
3. "whetehr to forbid the standout" -> "Redirect stdout to /dev/null"
Have you verified that the absence of logs doesn't trip up the Nodemanager when it tries to
go collect them? Could you please also do this for stderr?

[~chris.douglas] What do you think?

> Provide option  to forbid stdout of MapReduce task
> --------------------------------------------------
>
>                 Key: MAPREDUCE-6220
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6220
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>            Reporter: Yang Hao
>            Assignee: Yang Hao
>         Attachments: MAPREDUCE-6220.patch, MAPREDUCE-6220.v2.patch
>
>
> System.out is a ugly way to print log, and many times it would do harm to Hadoop cluster.
So we can provide an option to forbid it



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

Mime
View raw message