[
https://issues.apache.org/jira/browse/TEZ-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993009#comment-15993009
]
Kuhu Shukla commented on TEZ-3705:
----------------------------------
{quote} if (ShuffleUtils.isTezShuffleHandler(getConfig())) {
Not sure why this condition is required in ContainerLauncherManager?
{quote}
This is mostly for an early out from the dagComplete in case we are not using
tez_shuffle. We can remove this (and get rid of the import) and let it drop out
later based on the same check. I will put up a patch with that and additional
comments addressed. Thanks [~sseth].
> 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
>
>
> 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)
