tencent cloud

Elasticsearch Service

User Guide
Release Notes and Announcements
Release Notes
Product Announcements
Security Announcement
Product Introduction
Overview
Elasticsearch Version Support Notes
Features
Elastic Stack (X-Pack)
Strengths
Scenarios
Capabilities and Restrictions
Related Concepts
Purchase Guide
Billing Overview
Pricing
Elasticsearch Service Serverless Pricing
Notes on Arrears
ES Kernel Enhancement
Kernel Release Notes
Targeted Routing Optimization
Compression Algorithm Optimization
FST Off-Heap Memory Optimization
Getting Started
Evaluation of Cluster Specification and Capacity Configuration
Creating Clusters
Accessing Clusters
ES Serverless Guide
Service Overview
Basic Concepts
5-Minute Quick Experience
Quick Start
Access Control
Writing Data
Data Query
Index Management
Alarm Management
ES API References
Related Issues
Data Application Guide
Data Application Overview
Data Management
Elasticsearch Guide
Managing Clusters
Access Control
Multi-AZ Cluster Deployment
Cluster Scaling
Cluster Configuration
Plugin Configuration
Monitoring and Alarming
Log Query
Data Backup
Upgrade
Practical Tutorial
Data Migration and Sync
Use Case Construction
Index Configuration
SQL Support
Receiving Watcher Alerts via WeCom Bot
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Types
Error Codes
FAQs
Product
ES Cluster
Service Level Agreement
Glossary
New Version Introduction
Elasticsearch Service July 2020 Release
Elasticsearch Service February 2020 Release
Elasticsearch Service December 2019 Release

Restarting Clusters

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2022-11-10 16:57:28

Operation scenarios

ES provides a cluster restart feature that allows you to restart your cluster as needed.

Notes

1. Restarting a cluster is time-consuming; therefore, you are not recommended to do so unless necessary.
2. During the restart process, all nodes will be restarted one by one. Therefore, you should ensure that your cluster has at least one replica; otherwise, your cluster will change to RED health status or even incur a risk of data loss.
3. If the health status of your cluster is YELLOW or RED, or there is an index that has no replicas, you will be prompted to force restart your cluster when performing a restart operation, which involves a high risk of data loss. In this case, you are recommended to restore the status of your cluster to GREEN first and create at least one replica for all indices before proceeding. If the status of your cluster cannot be restored, and you still want to restart it after becoming aware of the risk involved in a force restart, you can check the force restart option to restart your cluster.

Directions

1. Log in to the ES Console.
2. You can restart your cluster either on the cluster list page or the cluster details page.
On the cluster list page, select a cluster and then select Operation > More > Restart.
Click the cluster name to enter the cluster details page, and select More > Restart in the top-right corner.
3. The following screen will appear after you click Restart. After you click OK, the cluster status will change to "processing", and the restart operation will be finished once the cluster status is restored to normal.



4. If the cluster status is YELLOW or RED, or there is an index in your cluster that has no replicas, a force restart prompt will appear as shown below, and you can only initiate a restart operation by checking "Force Restart". In this case, you can refer to the description in item 3 of Notes. After you initiate the restart operation, the cluster status will change to "processing", and the restart operation will be finished once the cluster status is restored to normal.




Ajuda e Suporte

Esta página foi útil?

comentários