You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/06/08 06:19:00 UTC

[jira] [Updated] (HIVE-29651) Update ZookeeperExternalSessionsRegistryClient to handle multiple HiveServer2 instances submitting DAGs concurrently to available Tez External Sessions

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

ASF GitHub Bot updated HIVE-29651:
----------------------------------
    Labels: pull-request-available  (was: )

> Update ZookeeperExternalSessionsRegistryClient to handle multiple HiveServer2 instances submitting DAGs concurrently to available Tez External Sessions
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-29651
>                 URL: https://issues.apache.org/jira/browse/HIVE-29651
>             Project: Hive
>          Issue Type: Bug
>            Reporter: tanishqchugh
>            Assignee: tanishqchugh
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, ZookeeperExternalSessionsRegistryClient tracks the availability of Tez AMs using local HashSets. In deployments with multiple HS2 instances, this state is not synchronized across all the HS2 instances. Consequently, when one HS2 occupies a Tez AM by submitting a DAG, the other HS2 instances remain unaware of this status change. This causes out-of-sync HS2s to submit new DAGs to already-occupied Tez AMs, resulting in execution errors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)