[jira] [Updated] (TEZ-3509) Make DAG Deletion path based

["Kuhu Shukla (JIRA)" <ji...@apache.org>]

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

Kuhu Shukla updated TEZ-3509:
-----------------------------
    Attachment: TEZ-3509.001.patch

Initial patch that introduces DeletionTracker that builds the url and inits the {{dagDeleteRunnable}} for deletion. This tracker also maintains the {{nodeIdShufflePortMap}} instead of the individual ContainerLaunchers. ServicePluginName is passed to the tracker as well.

The ShuffleHandler expects a path for deletion now, which is built through ShuffleUtils helper methods.
The deletionTracker is instantiated per ContainerLauncherImpl.
[~jeagles]/[~sseth] Appreciate some ideas/comments on this approach.

> Make DAG Deletion path based
> ----------------------------
>
>                 Key: TEZ-3509
>                 URL: https://issues.apache.org/jira/browse/TEZ-3509
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>         Attachments: TEZ-3509.001.patch
>
>
> The idea here is to have the API take a path to delete, be it DAG path today or a vertex level path later on. The current implementation takes a flag which is specific to DAG deletion. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)