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

ZooKeeperHiveLockManager.getQuorumServers incorrectly appends the custom zk port to quorum hosts

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.12.0
    • 0.13.0
    • Locking
    • None

    Description

      ZooKeeperHiveLockManager calls the below method to construct the connection string for ZooKeeper connection.

        private static String getQuorumServers(HiveConf conf) {
          String hosts = conf.getVar(HiveConf.ConfVars.HIVE_ZOOKEEPER_QUORUM);
          String port = conf.getVar(HiveConf.ConfVars.HIVE_ZOOKEEPER_CLIENT_PORT);
          return hosts + ":" + port;
        }
      

      For example:
      HIVE_ZOOKEEPER_QUORUM=node1, node2, node3
      HIVE_ZOOKEEPER_CLIENT_PORT=9999

      Connection string given to ZooKeeper object is "node1, node2, node3:9999". ZooKeeper consider the default port as 2181 for hostnames that don't have any port.

      This works fine as long as HIVE_ZOOKEEPER_CLIENT_PORT is 2181. If it is different then ZooKeeper client object tries to connect to node1 and node2 on port 2181 which always fails. So it has only one choice the last host which receives all the load from Hive.

      Attachments

        1. HIVE-5643.1.patch.txt
          3 kB
          Venki Korukanti

        Activity

          People

            vkorukanti Venki Korukanti
            vkorukanti Venki Korukanti
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: