[
https://issues.apache.org/jira/browse/TEZ-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991366#comment-13991366
]
Hitesh Shah commented on TEZ-693:
---------------------------------
bq. How can we check this? This un-registration occurs through
taskSchedulerEventHandler.setShouldUnregisterFlag(). right? In that case, we
can write a common method that all un-registration path will call and we will
inject our deleteOnExit() there. does it make sense?
Agreed. The code will likely need some changes with eventually, the
DAGAppMaster being the source of truth for this flag and when the flag is set,
it could make the necessary calls to all required services as needed.
> Deletion of DAG specific data after DAG completion
> --------------------------------------------------
>
> Key: TEZ-693
> URL: https://issues.apache.org/jira/browse/TEZ-693
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Mohammad Kamrul Islam
>
> Currently the client uploads some dag specific data to a remote directory
> specified by the user. The burden is on the client to clean this data after
> the dag completes. The post dag completion code in the AM should be able to
> clean this custom uploaded data.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
