[ 
https://issues.apache.org/jira/browse/TEZ-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937579#comment-17937579
 ] 

Hadoop QA commented on TEZ-3991:
--------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} TEZ-3991 does not apply to master. Rebase required? Wrong Branch? 
See https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | TEZ-3991 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12964794/TEZ-3991.3.patch |
| Console output | 
https://ci-hadoop.apache.org/job/PreCommit-TEZ-Build/133/console |
| versions | git=2.34.1 |
| Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |


This message was automatically generated.



> 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)

Reply via email to