Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-9119

ZooKeeperHiveLockManager does not use zookeeper in the proper way

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.13.0, 0.13.1, 0.14.0
    • 1.1.0
    • Locking

    Description

      ZooKeeperHiveLockManager does not use zookeeper in the proper way.

      Currently a new zookeeper client instance is created for each getlock/releaselock query which sometimes causes the number of open connections between
      HiveServer2 and ZooKeeper exceed the max connection number that zookeeper server allows.

      To use zookeeper as a distributed lock, there is no need to create a new zookeeper instance for every getlock try. A single zookeeper instance could be reused and shared by ZooKeeperHiveLockManagers.

      Attachments

        1. HIVE-9119.1.patch
          28 kB
          Na Yang
        2. HIVE-9119.2.patch
          31 kB
          Na Yang
        3. HIVE-9119.3.patch
          30 kB
          Na Yang
        4. HIVE-9119.4.patch
          31 kB
          Na Yang

        Issue Links

          Activity

            People

              nyang Na Yang
              nyang Na Yang
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: