Supporting CDP components
The following table lists the components and the layout for a five node cluster.
Service | Node 1 (All master components of all services) |
Node 2, 3, 4 (Worker nodes + ZooKeeper + Cloudera Observability processing components) |
Node 5 (Worker nodes + Cloudera Observability processing components + Cloudera Observability UI ) |
---|---|---|---|
Cloudera Management |
|
||
HBase |
|
|
|
HDFS |
|
|
|
Hive |
|
|
|
Hue (Optional) |
|
||
Impala |
|
|
|
Kafka |
|
||
Phoenix |
|
|
Configuring multiple Phoenix Query Server hosts reduces bottlenecks. The number of Phoenix Query Server hosts must be proportional to the number of Cloudera Observability On-Premises roles. For example, if you have roles on 5 nodes, at least 5 Query Servers are recommended for Phoenix. Cloudera Observability On-Premises internally balances loads on those hosts. |
ZooKeeper |
|
* To enable High Availability for
Impala across daemons, you can manually configure multiple hosts by setting up
HAProxy. For information, see Apache Impala documentation.