Node Type Description

Last updated: 2021-06-01 17:27:00

    EMR offers five types of nodes for your choice based on the cluster type.

    Hadoop Cluster

    Node Type Description HA Node Quantity Non-HA Node Quantity
    Master Processes such as NameNode, ResourceManager, and HMaster are deployed here. 2 1
    Core Processes such as DataNode, NodeManager, and RegionServer are deployed here. ≥ 3 ≥ 2
    Task Processes such as NodeManager and PrestoWork are deployed here. The number of task nodes can be changed at any time to scale the cluster. The minimum value is 0.
    Common Distributed coordinator components such as ZooKeeper and JournalNode are deployed here. ≥ 3 0
    Router Hadoop packages, including software programs and processes such as Hive, Hue, and Spark, are deployed here. The number of router nodes can be changed at any time. The minimum value is 0.
    • A master node is a management node that ensures that the scheduling of the cluster works properly.
    • A core node is a compute and storage node. All your data in HDFS is stored in core nodes. Therefore, in order to ensure data security, once core nodes are scale out, they cannot be scaled in.
    • A task node is a pure compute node and does not store any data. The computed data comes from a core node or COS. Therefore, it is often used as an elastic node and can be scaled in or out at any time.
    • A common node provides data sharing and syncing and HA fault tolerance services for the master nodes in an HA cluster.
    • A router is used to share the load of a master node or as the task submitter of the cluster. It can be scaled in or out at any time.

    ClickHouse Cluster

    Node Type Description HA Node Quantity Non-HA Node Quantity
    Core The ClickHouseServer process is deployed here. ≥ 2 ≥ 1
    Common Distributed coordinator components such as ZooKeeper are deployed here. ≥ 3 0
    • A core node is a compute and storage node.
    • A common node provides data sharing and syncing and HA fault tolerance services for the master nodes in an HA cluster.

    Druid Cluster

    Node Type Description HA Node Quantity Non-HA Node Quantity
    Master Processes such as NameNode, ResourceManager, Overlord, coordinator, ZKFailoverController, and JobHistoryServer are deployed here. 2 1
    Core Processes such as DataNode, NodeManager, middlemanager, and historical are deployed here. ≥ 3 ≥ 2
    Task Processes such as NodeManager and middlemanager are deployed here. The number of task nodes can be changed at any time to scale the cluster. The minimum value is 0.
    Common Distributed coordinator components such as ZooKeeper and JournalNode are deployed here. ≥ 3 0
    Router Hadoop packages, including software programs and processes such as broker, are deployed here. The number of router nodes can be changed at any time. The minimum value is 0.
    • A master node is a management node that ensures that the scheduling of the cluster works properly.
    • A core node is a compute and storage node. All your data in HDFS is stored in core nodes. Therefore, in order to ensure data security, once core nodes are scale out, they cannot be scaled in.
    • A task node is a pure compute node and does not store any data. The computed data comes from a core node or COS. Therefore, it is often used as an elastic node and can be scaled in or out at any time.
    • A common node provides data sharing and syncing and HA fault tolerance services for the master nodes in an HA cluster.
    • A router is used to share the load of a master node or as the task submitter of the cluster. It can be scaled in or out at any time.

    Kafka Cluster

    Node Type Description HA Node Quantity Non-HA Node Quantity
    Core Processes such as Kafka and KafkaManager are deployed here. ≥ 2 ≥ 1
    Common Distributed coordinator components such as ZooKeeper are deployed here. ≥ 3 0
    • A core node is a compute and storage node.
    • A common node provides data sharing and syncing and HA fault tolerance services for the core nodes in an HA cluster.

    Doris Cluster

    Node Type Description HA Node Quantity Non-HA Node Quantity
    Master Processes such as FE Follower and Broker are deployed here. ≥ 3 ≥ 1
    Core Processes such as BE and Broker are deployed here. ≥ 3
    Router Processes such as FE Observer and Broker are deployed here. The number of router nodes can be changed at any time. The minimum value is 0.
    • A master node is a frontend module and provides the Web UI feature.
    • A core node is a backend module and provides the data storage feature.
    • A router node is a frontend module and helps achieve high read/write availability.