[
https://issues.apache.org/jira/browse/TEZ-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937575#comment-17937575
]
Shohei Okumiya commented on TEZ-3991:
-------------------------------------
I'm interested in this umbrella. I ported the attached patch so we can grab the
change on GitHub. I'm still learning what the patch is doing.
https://github.com/okumin/tez/commit/c687c7cae31c68e9a738617b4c6c5b6e95f89ec2
> 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, TEZ-3991.2.patch, TEZ-3991.3.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
(v8.20.10#820010)
