tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TEZ-3705) Modify DeletionTracker and deletion threads to be initialized only if enabled for tez_shuffle
Date Thu, 04 May 2017 20:34:04 GMT

     [ https://issues.apache.org/jira/browse/TEZ-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Eagles resolved TEZ-3705.
----------------------------------
       Resolution: Fixed
    Fix Version/s: TEZ-3334

Committed to the TEZ-3334 feature branch.

> 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
>             Fix For: TEZ-3334
>
>         Attachments: TEZ-3705.001.patch, TEZ-3705.002.patch, TEZ-3705.003.patch, TEZ-3705.004.patch,
TEZ-3705.005.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)

Mime
View raw message