01-22-2019 09:37 PM - last edited on 01-23-2019 07:56 AM by cjervis
We set up and verify with reference to the following HA setting procedure of HS2.
In the case of a cluster where Hue cooperates with Hive,
When LB fails, set the "HiveServer 2 Load Balancer property" setting on the Web GUI of Cloudera Manager (CM) to the FQDN: port of HS2 and restart the service, the following updated settings were confirmed.
For DOC, "HiveServer 2 Load Balancer property" is a property to be used by specifying LB, but is it not possible to specify that using HS2 is out of the support range? (Is it within the scope of correct use as a product?)
* Example 1: In the case of a cluster which deploy one LB and HS2 HA, when LB failure, set "HiveServer 2 Load Balancer property" to HS2 host and port.
* Example 2, In the case of a cluster which deploy one LB and HS2 HA, when the default connection destination HS2 fails, set "HiveServer 2 Load Balancer property" to other HS2 host and port.
Since "HiveServer 2 Load Balancer property" can only specify one LB, by changing the setting as described above, it is possible to recover quickly in the case of node failure(etc) having a long time I think.
In addition, I confirm that the same applies to Kerberized clusters.
thank you for reading.