[
https://issues.apache.org/jira/browse/MAPREDUCE-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282103#comment-13282103
]
Ahmed Radwan commented on MAPREDUCE-4284:
-----------------------------------------
Arun, the idea here is to allow the option of inspecting container logs/local
dirs without the need to change a NM property which will require restarting all
NMs in the whole cluster (which doesn't seem feasible on a real cluster). Also
it is not useful to generalize the behavior for all jobs when the requirement
is to inspect a single failing job for example.
I am contrasting this behavior to the older behavior we had with
keep.failed.task.files property which was per-job. What do you think? What are
the type of attacks you are worried about?
> Allow setting yarn.nodemanager.delete.debug-delay-sec on a per-job basis
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-4284
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4284
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Ahmed Radwan
> Assignee: Ahmed Radwan
>
> The yarn.nodemanager.delete.debug-delay-sec property is helpful in debugging
> jobs (inspecting container logs/local dirs after the job finishes). Currently
> it is a nodemanager property and changing it requires restarting the
> nodemanager. In a production cluster this can be a real problem. It is better
> to have this property set on a per-job basis and not requiring the restart of
> nodemanagers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
