Skip to main content



Load Balance or dynamic discovery of HiveServer2 Connection from Beeline or Hive Shell


To provide high availability or load balancing for HiveServer2, Hive provides a function called dynamic service discovery where multiple HiveServer2 instances can register themselves with Zookeeper. Instead of connecting to a specific HiveServer2 directly, clients connect to Zookeeper which returns a randomly selected registered HiveServer2 instance.


For example - 

Below command connects to Hive Server on MachineA

  • beeline -u "jdbc:hive2://machineA:10000"

Below command connects to Zookeeper Node: to determine one of the available Hive Server's to make a connection

  • beeline -u "jdbc:hive2://machineA:2181,machineB:2181,machineC:2181/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2-mob-batch?tez.queue.name=myyarnqueue"

We can Create ZNode with Zookeeper as follows - 

  1. Open Zookeeper command line interface
    • zookeeper-client
  2. Connect to Zookeeper Server
    • connect machineA:2181,machineB:2181,machineC:2181
  3. Create ZNode
    • create /hiveserver2-mob-batch
  4. Manually, Register HS2 with Zookeeper under a namespace
    • create /hiveserver2-mob-batch/serverUri=machineA:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000082
    • create /hiveserver2-mob-batch/serverUri=machineB:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000081
    • create /hiveserver2-mob-batch/serverUri=machineC:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000051
  5. Verify the Namespace by executing below
    • ls /hiveserver2-mob-batch
    • [serverUri=machineC:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000051, serverUri=machineA:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000082, serverUri=machineB:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000081]

To deregister a particular HiveServer2, in the Zookeeper command line interface, run the following command
  • delete /hiveserver2-mob-batch/serverUri=machineC:10000;version=3.1.3000.7.1.2.0-96;sequence=0000000051
After you deregister the HiverServer2 from Zookeeper, it will not return the deregistered HiveServer2 for new client connections. However, any active client session is not affected by deregistering the HiveServer2 from Zookeeper.

To deregister all HiveServer2 instances of a particular version, run the following command from the command line:
  • hive --service hiveserver2 --deregister <version_number>

Now, Even after,  we do above manual configuration in Zookeeper. We might still get an error like below, when invoking beeline/ hive - 

22/04/11 19:43:31 [main-EventThread]: ERROR imps.EnsembleTracker: Invalid config event received: {server.1=machineA:3181:4181:participant, version=0, server.3=machineB:3181:4181:participant, server.2=machineC:3181:4181:participant}
Error: org.apache.hive.jdbc.ZooKeeperHiveClientException: Unable to read HiveServer2 configs from ZooKeeper (state=,code=0)

This is because following steps needs to ensured by Admin Team for zookeeper discovery for HS2

Configuration Requirements

1. Set hive.zookeeper.quorum to the ZooKeeper ensemble (a comma separated list of ZooKeeper server host:ports running at the cluster)

2. Customize hive.zookeeper.session.timeout so that it closes the connection between the HiveServer2’s client and ZooKeeper if a heartbeat is not received within the timeout period.

3. Set hive.server2.support.dynamic.service.discovery to true

4. Set hive.server2.zookeeper.namespace to the value that you want to use as the root namespace on ZooKeeper. The default value is hiveserver2.

5. The adminstrator should ensure that the ZooKeeper service is running on the cluster, and that each HiveServer2 instance gets a unique host:port combination to bind to upon startup. 



As a developer, we applied following hack to get random HiveServer2 from Zookeper. Thus, distributing load across HS2- 

beeline -u "jdbc:hive2://$( ( echo "connect machineA:2181,machineB:2181,machineC:2181"; echo "ls /hiveserver2-mob-batch") | zookeeper-client | grep -oP '(?<=serverUri=).*?(?=;)'| shuf | head -1)/default;principal=hive/_HOST@MYDOMAIN"

What above command is doing - 
  1. Open zookeeper-client
    1. connect machineA:2181,machineB:2181,machineC:2181
    2. ls /hiveserver2-mob-batch
  2. Parse HS2 URL's, as mentioned between - serverUri=  and ;
  3. Does Random shuffling of all URL's - shuf
  4. Pick up first random URL - head -1
  5. Concatenate string to form JDBC URL - jdbc:hive2:// ...


Comments

Post a Comment

Popular posts

Unix Server ( Edge Node ) hangs when there are many jobs running on hadoop cluster started from Unix Edge Node.

  When a unix server or an edge node is running lots of jobs (like Spark, Hadoop, or custom batch processes), crashes happen. For example. For example a process might hit a segementation fault, memory issue or ay other runtime issue. By default, if ulimit -c is not 0, the OS will create core dump. Core dump are written to disk and can be very large, sometimes hundreds of MBs or even GBs per process. What we realized was that when multiple processes crash at the same time, the system suddenly tries to write core files to disk. This was leading to DisK I/O spikes. Thus, node was becoming unresponsive. This was also leading CPU spike because OS was handling crash logging. Setting "ulimit -c 0" disables core dumps. This way we lose ability to debug crashes via core dump But, kept production edge nodes stable. On most Linux systems, by default, "core dumps" are written in current working directory of the process that crashes. Linux allows you to change core dump file nam...
Post a Comment
Read more




VPN testing checklist

 To test: Is VPN active? Is it leaking? Does it look residential? Does it alter network fingerprints? Public IP Test (Basic Detection) - curl ipinfo.io DNS Leak Test - nslookup google.com MTU Test (Encapsulation Detection) - ping 8.8.8.8 -f -l 1472 TCP MSS Inspection - Use Wireshark and Look for SYN packets. Traceroute Path Test - tracert 8.8.8.8 WebRTC Leak Test - browserleaks.com/webrtc IPv6 Leak Test - test-ipv6.com Latency / Jitter Test - ping -n 50 8.8.8.8. VPN usually causes: More Jitters and Latency. Reverse DNS (PTR Record) - nslookup <your-public-ip> IP Reputation Check - Like most IP's from VPN Providers like Express VPN, etc. are blacklisted and all. Look for: Proxy/VPN classification, Hosting provider tagging
Post a Comment
Read more




Spark-JDBC connection with Oracle Fails - java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name

  While connecting Spark with Oracle JDBC, one may observe exception like below -  spark.read.format("jdbc"). option("url", "jdbc:oracle:thin:@//oraclehost:1521/servicename"). option("dbtable", "mytable"). option("user", "myuser").option("driver", "oracle.jdbc.driver.OracleDriver") option("password", "mypassword"). load().write.parquet("/data/out") java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208) ...
Post a Comment
Read more




Spring MongoDB Rest API not returning response in 90 seconds which is leading to client timeout

  We have Spring Boot  Rest API deployed in Kubernetes cluster which integrates with MongoDB to fetch the data.  MongoDB is fed with data by a real time Spark & NiFi job.  Our clients complained that for a request what they send they don't have response within 90 seconds. Consider it like an OMS ( Order ManagEment System).  On further analysis, we found that Spark & NiFi processing is happenning within 10 seconds after consuming response data from Kafka. Thus, initally out thought was that it due to delay from upstream to produce data in to Kafka.  Thankfully, our data had create / request  timestamp, and when response was received, and when response was inserted into MongoDB. Subtracting response insert time from request time seemed to be well within 90 seconds. But, still client did timeout on not seeing a response within 90 seconds. This led to confusion on our side.  But, then we realized it was due to Read Preference . We updated this...
Post a Comment
Read more




MongoDB Regex Query taking more time in Production but same query perform well in UAT

   We came across a situation where-in, MongoDB Query was taking more time in Production like 10 seconds and 4.2 seconds but same query performed well in UAT taking under 400 ms. The very first thought that was evident to us that it is because of amount of data which differed in UAT and Production. Then we ran following to see the execution plan -   db.collection.aggregate(<queries>).explain() This gave us Winning and Rejected Plans. Under which, we analyzed that although it was using 'IXSCAN.' But, it was incorrect index- as we had one compound index built on time field and other fields, and there was other index just on time field for TTL purposes. Winning plan picked TTL index rather than compound index. Thus, we dropped TTL index and built TTL index on a different time field.  That got our query performance time from 10 seconds to 726 ms. Also, for other query the performance came down from 8 seconds to 4.3 seconds. Then, we ran following -  ...
Post a Comment
Read more