Hive
  1. Hive
  2. HIVE-3533

ZooKeeperHiveLockManager does not respect the option to keep locks alive even after the current session has closed

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 0.10.0
    • Component/s: Locking
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      The HiveLockManager interface defines the following method:

      public List<HiveLock> lock(List<HiveLockObj> objs,
      boolean keepAlive) throws LockException;

      ZooKeeperHiveLockManager implements HiveLockManager, but the current implementation of the "lock" method never actually references the "keepAlive" parameter. As a result, all of the locks acquired by the "lock" method are ephemeral. In other words, Zookeeper-based locks only exist as long as the underlying Zookeeper session exists. As soon as the Zookeeper session ends, any Zookeeper-based locks are automatically released.

        Activity

        Matt Martin created issue -
        Matt Martin made changes -
        Field Original Value New Value
        Attachment HIVE-3533.1.patch.txt [ 12547803 ]
        Matt Martin made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Namit Jain made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Hadoop Flags Reviewed [ 10343 ]
        Resolution Fixed [ 1 ]
        Ashutosh Chauhan made changes -
        Assignee Matt Martin [ matt.martin ]
        Ashutosh Chauhan made changes -
        Fix Version/s 0.10.0 [ 12320745 ]
        Ashutosh Chauhan made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Matt Martin
            Reporter:
            Matt Martin
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development