All Products
Search

This Product

    E-MapReduce:Add a service

    Document Center

    E-MapReduce:Add a service

    Last Updated:Jun 21, 2026

    You can add services to an E-MapReduce cluster after it is created. This topic describes how to add a service in the E-MapReduce console.

    Prerequisites

    A cluster has been created and is in the Running state. For more information about how to create a cluster, see Create a cluster.

    Limits

    • The cluster must be in the Running state.

    • All nodes in the cluster must be in the Running state, and all services must be healthy.

    • You can add services only to the following cluster types.

      Note

      • If you enable Kerberos Authentication when you create a cluster, you cannot add Knox or Kudu services after the cluster is created.

      • The services that you can add vary by E-MapReduce version. For the exact list, see the options in the console.

      Cluster type

      Supported services

      DataLake (EMR-3.43.0, EMR-5.9.0, and later)

      • Knox (requires OpenLDAP)

      • OpenLDAP

      • Ranger (requires Ranger-plugin and Hadoop-Common)

      • Iceberg

      • Hudi

      • JindoData (for EMR versions earlier than EMR-5.15.x and EMR-3.49.x)

      • JindoCache (for EMR 5.15.x and later, and EMR 3.49.x and later)

      • Presto/Trino (requires Hadoop-Common)

      • DLF-Auth

      • Tez (requires YARN)

      • Flume (requires Hadoop-Common)

      • RSS/Celeborn

      • Sqoop (requires YARN)

      • Kyuubi (requires Spark 3 and ZooKeeper)

      • Paimon

      • ZooKeeper

      DataFlow (EMR-3.43.0, EMR-5.9.0, and later)

      • Flink (requires YARN and OpenLDAP)

      • OpenLDAP

      • Knox (requires OpenLDAP)

      • Paimon

      • ZooKeeper

      DataServing (EMR-3.43.0, EMR-5.9.0, and later)

      • HBase (requires ZooKeeper and HDFS or OSS-HDFS)

      • Phoenix (requires HBase)

      • JindoData (for EMR versions earlier than EMR-5.15.x and EMR-3.49.x)

      • JindoCache (for EMR 5.15.x and later, and EMR 3.49.x and later)

      OLAP (EMR-3.43.0, EMR-5.9.0, and later)

      Adding services is not supported.

      Custom (EMR-3.43.0, EMR-5.9.0, and later)

      • Knox (requires OpenLDAP)

      • OpenLDAP

      • Ranger (requires Ranger-plugin and Hadoop-Common)

      • Iceberg

      • Hudi

      • JindoData (for EMR versions earlier than EMR-5.15.x and EMR-3.49.x)

      • JindoCache (for EMR 5.15.x and later, and EMR 3.49.x and later)

      • Presto (requires Hadoop-Common)

      • DLF-Auth

      • Tez (requires YARN)

      • Flume (requires Hadoop-Common)

      • RSS/Celeborn

      • Flink (requires YARN and OpenLDAP)

      • HBase (requires ZooKeeper and HDFS or OSS-HDFS)

      • Phoenix (requires HBase)

      Hadoop (New users can no longer create Hadoop clusters.)

      • Impala

      • Presto

      • Oozie

      • ZooKeeper

      • HBase

      • Zeppelin

      • Storm

      • Ranger

      • Superset

      • Livy

      • Flume

      • Kudu

      • ESS or RSS

    Usage notes

    After you add a service, some dependent services may require you to manually change their configurations and restart them. To minimize the impact on your business, perform this operation during off-peak hours.

    Procedure

    1. Go to the cluster Services page.

      1. Log on to the E-MapReduce console.

      2. In the left-side navigation pane, choose EMR on ECS.

      3. In the top navigation bar, select a region and resource group as needed.

      4. On the EMR on ECS page, find the target cluster and click Services in the Services column.

    2. On the Services tab, click Add Service.

    3. In the Add Service panel, select the service to add and click OK. Upon successful addition, a Service added successfully message appears, and the new service is listed on the current page.

      Note

      Some services require configuration changes to their dependencies after being added. After you select a service and click OK, the system highlights dependent services that require modification with an indicator. Review the indicators and proceed to the next step to modify the service configurations.

    4. Optional: Modify service configurations.

      For example, after you add the Trino service, you must modify the configurations for the Hive, Spark 3, Tez, Trino, and YARN services.

      1. On the Services page, click Configure for any service that displays an indicator.

      2. In the notification area, click Modify Configurations.

      3. In the Modify Configurations panel, select all configuration items and click Save. The Save and Deliver Configuration switch is enabled by default.

      4. Restart the related services for the changes to take effect. For more information, see Restart a Service.

        After you modify the configuration, a Pending tag appears on related services, such as Trino. This tag indicates that you must restart the service for the changes to take effect.

    Related documentation