This section provides an example of configuring Cloudera Manager for high availability using a TCP load balancer. The procedures describe how to configure high availability using a specific, open-source load balancer. Depending on the operational requirements of your CDH deployment, you can select a different load balancer. You can use either a hardware or software load balancer, but must be capable of forwarding all Cloudera Manager ports to backing server instances. (See Ports Used by Cloudera Manager and Cloudera Navigator for more information about the ports used by Cloudera Manager.)

This topic discusses Cloudera Manager high availability in the context of active-passive configurations only; active-active configurations are currently unsupported. For more information about the differences between active-passive and active-active High Availability, see http://en.wikipedia.org/wiki/High-availability_cluster.

  Important: Cloudera Support supports all of the configuration and modification to Cloudera software detailed in this document. However, Cloudera Support is unable to assist with issues or failures with the third-party software that is used. Use of any third-party software, or software not directly covered by Cloudera Support, is at the risk of the end user.

  Warning: Cloudera Navigator Audit and Lineage do not support this high availability configuration. Cloudera Navigator will only be available on one of the two Cloudera Manager server hosts. If a failover is triggered, Cloudera Manager may fail over to a host where Cloudera Navigator is not available and data loss may result.

Continue reading:

• Introduction to Cloudera Manager Deployment Architecture
• Prerequisites for Setting up Cloudera Manager High Availability
• Cloudera Manager Failover Protection
• High-Level Steps to Configure Cloudera Manager High Availability
• Database High Availability Configuration
• TLS and Kerberos Configuration for Cloudera Manager High Availability