Configuring HiveServer high availability using ZooKeeper
You need to know how to configure your Hive-on-Tez to use ZooKeeper for HiveServer high availability.
When a client requests an HS2 instance, ZooKeeper returns one randomly-selected registered HS2. If more than one HS2 instance is registered with ZooKeeper, and all instances fail except one, ZooKeeper passes the link to the instance that is running and the client can connect successfully. (Failed instances must be restarted manually.)
Automatic failover does not occur. If an HS2 instance failed while a client is connected, the session is lost. Since this situation need to be handed at the client, there is no automatic failover; the client needs to reconnect using ZooKeeper.
Using binary transport mode in HiveServer (HS2), Knox, and Dynamic Discovery, possibly supported on your platform before upgrading to CDP, are not supported on CDP. Use alternate solutions, such as HAProxy.