hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Vasudev (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-5600) Add a parameter to ContainerLaunchContext to emulate yarn.nodemanager.delete.debug-delay-sec on a per-application basis
Date Thu, 17 Nov 2016 15:59:58 GMT

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

Varun Vasudev edited comment on YARN-5600 at 11/17/16 3:59 PM:
---------------------------------------------------------------

[~miklos.szegedi@cloudera.com] - can you explain when the container and application resources
will be cleaned up in the following scenarios -
1)
yarn.nodemanager.delete.debug-delay-sec=600
delete.max-per-application-debug-delay-sec=300
container sets DEBUG_DELETE_DELAY to 200

2)
yarn.nodemanager.delete.debug-delay-sec=600
delete.max-per-application-debug-delay-sec=300
container sets DEBUG_DELETE_DELAY to 400

3)
yarn.nodemanager.delete.debug-delay-sec=300
delete.max-per-application-debug-delay-sec=600
container sets DEBUG_DELETE_DELAY to 600

Thanks!


was (Author: vvasudev):
[~miklos.szegedi@cloudera.com] - can you explain when the container and application resources
will be cleaned up in the following scenarios -
1)
yarn.nodemanager.delete.debug-delay-sec=600
delete.max-per-application-debug-delay-sec=300
container sets DEBUG_DELETE_DELAY to 200

2)
yarn.nodemanager.delete.debug-delay-sec=600
delete.max-per-application-debug-delay-sec=300
container sets DEBUG_DELETE_DELAY to 400

3)
yarn.nodemanager.delete.debug-delay-sec=300
delete.max-per-application-debug-delay-sec=600
container sets DEBUG_DELETE_DELAY to 600

Thanks!

Thanks!

> 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
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Daniel Templeton
>            Assignee: Miklos Szegedi
>              Labels: oct16-medium
>         Attachments: YARN-5600.000.patch, YARN-5600.001.patch, YARN-5600.002.patch, YARN-5600.003.patch,
YARN-5600.004.patch, YARN-5600.005.patch, YARN-5600.006.patch, YARN-5600.007.patch, YARN-5600.008.patch,
YARN-5600.009.patch, YARN-5600.010.patch, YARN-5600.011.patch, YARN-5600.012.patch, YARN-5600.013.patch,
YARN-5600.014.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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message