Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
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.