When you create an E-MapReduce (EMR) cluster, the services that can be deployed on the cluster nodes vary based on the cluster type. After the cluster is created and runs as normal, you can manage the services in the cluster. You can add, configure, start, stop, and restart the services. This topic describes how to restart a service in the EMR console.


An EMR cluster is created. For more information, see Create a cluster.


  • To minimize impacts on business operations, we recommend that you restart a service in rolling mode. For instances deployed in primary/secondary mode, restart the service on the secondary instance and then the service on the primary instance.
  • If you clear Rolling Execute, the service is restarted on all nodes at the same time. In this case, the service stops running during the restart. Proceed with caution.


After you modify the configurations of a service, you must restart the service to make the configurations take effect. You can configure, start, and stop services on the Services tab.

  1. Go to the Services tab.
    1. Log on to the EMR console.
    2. In the top navigation bar, select the region where your cluster resides and select a resource group based on your business requirements.
    3. On the EMR on ECS page, click Services in the Actions column of the cluster that you want to manage.
  2. On the Services tab, choose more > Restart for the service that you want to restart.
    You can also go to the Configure tab of the service and then choose More > Restart.
  3. In the dialog box that appears, enter a reason and click OK.
    The following table describes the parameters that you can configure.
    Rolling ExecutionThis feature is enabled by default. After this feature is enabled, the system runs tasks at the interval specified in Rolling Execution Interval. The Rolling Execution Interval parameter specifies the time interval between two consecutive tasks that are executed.
    Failure Handling Policy
    • Proceed Upon Failure of Single Node: When the system runs a task, if a node fails to pass the check, the system runs the task on other healthy nodes.
    • Stop Upon Failure of Single Node: When the system runs a task, if a node fails to pass the check, the system terminates the task.
    Execution ReasonThe reason for the task.
  4. After you confirm the information in the Confirm message, click OK.
    Then, the system prompts The operation is successful.. The system will run the task based on the policy that you configured.