You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "D M Murali Krishna Reddy (Jira)" <ji...@apache.org> on 2020/09/16 09:10:00 UTC
[jira] [Updated] (YARN-10437) Destroy yarn service if any
YarnException occurs during submitApp
[ https://issues.apache.org/jira/browse/YARN-10437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
D M Murali Krishna Reddy updated YARN-10437:
--------------------------------------------
Attachment: YARN-10437.002.patch
> Destroy yarn service if any YarnException occurs during submitApp
> -----------------------------------------------------------------
>
> Key: YARN-10437
> URL: https://issues.apache.org/jira/browse/YARN-10437
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-native-services
> Reporter: D M Murali Krishna Reddy
> Assignee: D M Murali Krishna Reddy
> Priority: Minor
> Attachments: YARN-10437.001.patch, YARN-10437.002.patch
>
>
> If a user submits a yarn service with configuration such that it causes an exception during application submission, the files related to the service are not cleared from hdfs automatically. Ideally the files stored to hdfs cannot be used in future to start or stop the service as the configuration itself is invalid. So, we should destroy the service and remove the residual files in hdfs, if any YarnException is thrown.
> For example if the user submits a service with configuring with "memory" more than the maximum resource, the service fails but the files in hdfs are not cleared. But these files should be cleared.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org