You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Eric Wohlstadter (JIRA)" <ji...@apache.org> on 2019/04/02 17:40:00 UTC

[jira] [Updated] (TEZ-3991) Unmanaged tez sessions

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

Eric Wohlstadter updated TEZ-3991:
----------------------------------
    Attachment: TEZ-3991.1.patch

> Unmanaged tez sessions
> ----------------------
>
>                 Key: TEZ-3991
>                 URL: https://issues.apache.org/jira/browse/TEZ-3991
>             Project: Apache Tez
>          Issue Type: New Feature
>    Affects Versions: 0.10.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Eric Wohlstadter
>            Priority: Major
>              Labels: Kubernetes
>         Attachments: TEZ-3991.1.patch
>
>
> Provide an option for launching tez AM in unmanaged mode. In unmanaged mode, tez AMs can register itself with Zookeeper which clients (like HiveServer2) can discover via zk registry client. 
> HiveServer2 currently manages the lifecycle of tez AMs. The unmanaged mode will let AM come up on their own (can be via simple java launcher) and be discoverable for others. 
> Example use case for this is, HiveServer2 can discover already running AMs and can attach to it for DAG submission and detach when done executing queries. AMs can similarly discover LLAP daemons via task scheduler plugin for submitting tasks. 
> A mode to cut off interactions with RM will also useful since for LLAP no on-demand containers are required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)