Configuring HMS for high availability
To provide failover to a secondary Hive metastore if your primary instance goes down, you need to know how to add a Metastore role in Cloudera Manager and configure a property.
Multiple HMS instances run in active/active mode. Load balancing is done at the Hive
client side (like HiveServer or Spark) as the HMS client picks an HMS instance
randomly. By default, the hive.metastore.uri.selection
property is
set to RANDOM. If that HMS instance is down, then the client randomly picks another
instance from the list of HMS instances specified through the
hive.metastore.uris
property.