[
https://issues.apache.org/jira/browse/TEZ-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997174#comment-15997174
]
Siddharth Seth commented on TEZ-3705:
-------------------------------------
Think the v5 patch is better. For sessions, which is presumably where dag
deletion is useful, the threadpool will eventually be created. It will
eventually be created - may as well create it up front.
+1. Thanks
> 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, TEZ-3705.005.patch, TEZ-3705.006.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)
