[
https://issues.apache.org/jira/browse/TEZ-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994156#comment-15994156
]
Siddharth Seth commented on TEZ-3705:
-------------------------------------
Thanks [~kshukla]
Since TEZ_AM_DAG_CLEANUP_ON_COMPLETION_DEFAULT is being checked in the various
container launchers, does it need to be checked again in DeletionTrackerImpl
also? Think DeletionTrackerImpl is simplified a bit if it assumes that the
threadpool is always enabled, and if the service is invoked, it will delete
data.
If the parameter is disabled, the services does not exist (or a dummy
implementation exists) - so deletions are avoided
> Modify DeletionTracker and deletion threads to be initialized only if enabled
> for tez_shuffle
> ---------------------------------------------------------------------------------------------
>
> Key: TEZ-3705
> URL: https://issues.apache.org/jira/browse/TEZ-3705
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Attachments: TEZ-3705.001.patch, TEZ-3705.002.patch,
> TEZ-3705.003.patch, TEZ-3705.004.patch
>
>
> Right now the Deletion Tracker and the associated threads are initialized
> irrespective of the deletion service being used/enabled or not. This can be
> made better.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
