Elastic MapReduce
- Release Notes and Announcements
- Announcements
- Security Announcements
- Product Introduction
- Product release
- Purchase Guide
- EMR on CVM Billing Instructions
- EMR on TKE Billing Instructions
- EMR Serverless HBase Billing Instructions
- Getting Started
- EMR on CVM Operation Guide
- Planning Cluster
- Cross-AZ Cluster
- Configuring Cluster
- Administrative rights
- Managing Cluster
- Auto Scaling
- Disk Management
- Managing Service
- Configuration Management
- YARN Resource Scheduling
- Monitoring and Alarms
- Application Analysis
- Monitoring Metrics
- EMR on TKE Operation Guide
- Configuring Cluster
- Permission Management
- Cluster Management
- Service Management
- Configuration Management
- Monitoring and Ops
- Application Analysis
- EMR Serverless HBase Operation Guide
- Planning an Instance
- Managing an Instance
- Monitoring and Alarms
- Development Guide
- EMR Development Guide
- Hadoop Development Guide
- Spark Development Guide
- Hbase Development Guide
- Phoenix on Hbase Development Guide
- Hive Development Guide
- Basic Hive Operations
- Advanced Usage
- Presto Development Guide
- Sqoop Development Guide
- Hue Development Guide
- Flume Development Guide
- Kerberos Development Guide
- Knox Development Guide
- Alluxio Development Guide
- Kylin Development Guide
- Livy Development Guide
- Kyuubi Development Guide
- Zeppelin Development Guide
- Hudi Development Guide
- Superset Development Guide
- Impala Development Guide
- Druid Development Guide
- TensorFlow Development Guide
- Kudu Development Guide
- Ranger Development Guide
- Ranger User Guide
- Kafka Development Guide
- StarRocks Development Guide
- Flink Development Guide
- Practical Tutorial
- Practice of EMR on CVM Ops
- Data Migration
- Practical Tutorial on Custom Scaling
- Practical Tutorial on Setting Scaling Rules
- API Documentation
- Making API Requests
- Cluster Resource Management APIs
- Cluster Services APIs
- FAQs
- EMR on CVM
Restarting Services
Last updated: 2024-10-30 11:07:54
Overview
After you upgrade the service roles or modify the configuration in a cluster, it is necessary to restart the corresponding service for the configuration to take effect. This document introduces the directions for restarting services through the console.
Directions
1. Log in to the EMR on TKE Console and click the Cluster ID/Name in the cluster list to enter the cluster details page.
2. If you need to restart the entire component service, select Cluster Service > Specific Service, and then choose Operations > Restart Service in the right-hand sidebar of the page. When you select the service role as ALL, the entire service will be restarted.
3. If you need to restart a specific role type of the service, you can select Cluster Service > Specific Service, check the service role that needs to be restarted on the role management page, and click Restart Service.
4. After the information is confirmed, click Confirm to restart the service.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No