[ https://issues.apache.org/jira/browse/TEZ-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Wohlstadter resolved TEZ-3875. ----------------------------------- Resolution: Duplicate Duplicates TEZ-3892 > Add "reconnect" API to TezClient for HSI HA > ------------------------------------------- > > Key: TEZ-3875 > URL: https://issues.apache.org/jira/browse/TEZ-3875 > Project: Apache Tez > Issue Type: New Feature > Affects Versions: 0.9.next > Reporter: Eric Wohlstadter > Priority: Major > > For HiveServer2 HA use cases with LLAP, launching a new Tez session (AM) > after failover adds non-interactive latency. Additionally, Tez with LLAP does > significant work to provision a long-lived session and hold on to necessary > resources allocated to it. We don't want to redo that work after failover and > potentially be unable to schedule equivalent resources that may be taken by > other applications during failover. > HS2 uses TezClient for creating sessions. To simplify HS2 failover to an > existing Tez AM, add a "reconnect" method to TezClient. > {code} > public void reconnect(ApplicationId) { ... } > {code} > {{reconnect}} will setup the TezClient context very similar to {{start}} > except it parameterizes the {{sessionAppId}} and doesn't launch a new AM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)