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

Popular posts

Spring MongoDB Rename field with derived Value of another field

Input Collection -  [ { 'k' : 'Troubleshooting' , 'hour' : '2024-10-10T16' , 'v' : [ 'WebPage, Login' ] }, { 'k' : 'TroubleshootingMe' , 'hour' : '2024-10-07T01' , 'v' : [ 'Accounts, etc' ] }  ] Expected Output -  [ { 'hour' : '2024-10-10T16' , 'Troubleshooting' : [ 'WebPage, Login' ] }, { 'hour' : '2024-10-07T01' , 'TroubleshootingMe' : [ 'Accounts, etc' ] }  ]   Above Can be achieved by  $replaceRoot / $replaceWith as follows - { $replaceWith : { $mergeObjects : [ { hour : "$hour" }, { "$arrayToObject" : [ [ { k : "$k" , v : "$v" } ] ] } ] } } or { $replaceRoo...




What is Leadership

 




Spark Error - missing part 0 of the schema, 2 parts are expected

 Exception -  Caused by: org.apache.spark.sql.AnalysisException : Could not read schema from the hive metastore because it is corrupted. (missing part 0 of the schema, 2 parts are expected).; Analysis -  ·          Check for table definition. In TBLProperties, you might find something like this – > spark.sql.sources.schema.numPartCols > 'spark.sql.sources.schema.numParts' 'spark.sql.sources.schema.part.0' > 'spark.sql.sources.schema.part.1' 'spark.sql.sources.schema.part.2' > 'spark.sql.sources.schema.partCol.0' > 'spark.sql.sources.schema.partCol.1' That’s what error seems to say that part1 is defined but part0 is missing.  Solution -  Drop & re-create table. If Table was partitioned  then all partitions  would have been removed. So do either of below -  ·          Msck repair table <db_name>.<table_name> ·    ...




Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...




Read from a hive table and write back to it using spark sql

In context to Spark 2.2 - if we read from an hive table and write to same, we get following exception- scala > dy . write . mode ( "overwrite" ). insertInto ( "incremental.test2" ) org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; 1. This error means that our process is reading from same table and writing to same table. 2. Normally, this should work as process writes to directory .hiveStaging... 3. This error occurs in case of saveAsTable method, as it overwrites entire table instead of individual partitions. 4. This error should not occur with insertInto method, as it overwrites partitions not the table. 5. A reason why this happening is because Hive table has following Spark TBLProperties in its definition. This problem will solve for insertInto met...