tencent cloud

Elastic MapReduce

Release Notes and Announcements
Release Notes
Announcements
Security Announcements
Product Introduction
Overview
Strengths
Architecture
Features
Use Cases
Constraints and Limits
Technical Support Scope
Product release
Purchase Guide
EMR on CVM Billing Instructions
EMR on TKE Billing Instructions
EMR Serverless HBase Billing Instructions
Getting Started
EMR on CVM Quick Start
EMR on TKE Quick Start
EMR on CVM Operation Guide
Planning Cluster
Administrative rights
Configuring Cluster
Managing Cluster
Managing Service
Monitoring and Alarms
TCInsight
EMR on TKE Operation Guide
Introduction to EMR on TKE
Configuring Cluster
Cluster Management
Service Management
Monitoring and Ops
Application Analysis
EMR Serverless HBase Operation Guide
EMR Serverless HBase Product Introduction
Quotas and Limits
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
Presto Development Guide
Sqoop Development Guide
Hue Development Guide
Oozie 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
Kafka Development Guide
Iceberg Development Guide
StarRocks Development Guide
Flink Development Guide
JupyterLab Development Guide
MLflow Development Guide
Practical Tutorial
Practice of EMR on CVM Ops
Data Migration
Practical Tutorial on Custom Scaling
API Documentation
History
Introduction
API Category
Cluster Resource Management APIs
Cluster Services APIs
User Management APIs
Data Inquiry APIs
Scaling APIs
Configuration APIs
Other APIs
Serverless HBase APIs
YARN Resource Scheduling APIs
Making API Requests
Data Types
Error Codes
FAQs
EMR on CVM
Service Level Agreement
Contact Us

Role Management

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2023-12-27 11:12:20

Overview

Role management provides Ops and operation features at the service role level. You can restart, pause, and maintain service roles at the node level. Role status can be monitored to help you stay on top of the real-time status of role processes.

Glossary

Restart: The nodes under the selected service role will be restarted on a rolling basis.
Pause: The nodes under the selected service role will be paused. They can be resumed by using the Start feature.
Maintenance: The process daemon will be stopped on the nodes under the selected service role, so when a process becomes abnormal for various reasons, no alarm or automatic recovery will occur. This is suitable for node debugging. You can use the Exit Maintenance feature to resume the daemon.

Directions

1. Log in to the EMR console and click the ID/Name of the target cluster in the cluster list to enter the cluster details page.
2. On the cluster details page, select Cluster Service and click Operation > Role Management in the top-right corner of the target component block. The following uses HDFS as an example.
3. The Role Management list displays the current service role's health status, operation status, configuration group, node type, maintenance status, server IP, and last restarted time. You can select a role and restart, maintain, start, or pause it.
Note
The Health Status column displays the running status of the current role. The Operation Status column displays user operations. The Maintenance Status column displays whether the role is under maintenance.


Health Status

Health Status
Description
Good
Port check is responded to within 5s.
Risky
Port check is responded to within 5s–10s.
Unavailable
Port check is not responded to within 10s.
Not checked
Roles in the maintenance mode or in Stopped operation status are not checked.
Unknown
The checker is abnormal or down.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백