[
https://issues.apache.org/jira/browse/YARN-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miklos Szegedi updated YARN-5600:
---------------------------------
Attachment: YARN-5600.000.patch
We delay the deletion of container resources specified by the container launch
parameters for debugging purposes. Before this change only a global
configuration entry was able to do this delaying all applications on the node,
not just one. Since the container directory is part of the the application
directory, we listen to the container completion event and delay the
application cleanup as well. The user is still able to specify to keep the
files forever, in which case we do not create a deletion task.
Testing: NodeManager unit tests passed and we also added task specific unit
tests to verify the new features.
> Add a parameter to ContainerLaunchContext to emulate
> yarn.nodemanager.delete.debug-delay-sec on a per-application basis
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-5600
> URL: https://issues.apache.org/jira/browse/YARN-5600
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Reporter: Daniel Templeton
> Assignee: Miklos Szegedi
> Attachments: YARN-5600.000.patch
>
>
> To make debugging application launch failures simpler, I'd like to add a
> parameter to the CLC to allow an application owner to request delayed
> deletion of the application's launch artifacts.
> This JIRA solves largely the same problem as YARN-5599, but for cases where
> ATS is not in use, e.g. branch-2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
