Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Restarting an Instance or a Node

Updated on 2024-08-08 GMT+08:00

You may need to occasionally restart an instance to perform routine maintenance. For example, after modifying certain parameters, the instance may need to be restarted to apply the changes.

Precautions

  • You can restart an instance only when its status is Available.
  • Restarting an instance will interrupt services. Exercise caution when performing this operation.
  • This instance is not available when it is being restarted. Restarting an instance will clear the cached memory in it. You are advised to restart it during off-peak hours.
  • If you restart a cluster or replica set instance, all nodes in the instance are also restarted.
  • You can restart a cluster instance or any dds mongos, shard, config node, or read replica in the cluster instance. During the restart, the node cannot be accessed.
  • You can restart a replica set instance. During the restart, the instance cannot be accessed.
  • You can restart any read replica in a replica set instance. During the restart, the node cannot be accessed.
    NOTE:

    Only whitelisted users can restart a read replica in a replica set instance. You need to submit a service ticket to apply for this function. In the upper right corner of the management console, choose Service Tickets > Create Service Ticket to submit a service ticket.

  • You can forcibly restart an abnormal node in a DB instance. The node cannot be accessed during the restart.
  • After a replica set instance is restarted, the node roles may change.
  • It takes less than 30 seconds to start a mongod or dds mongos process. If there are a large number of collections (more than 10,000), it may take several minutes to start the Mongod process. Before the startup is complete, the corresponding node cannot be connected. You are advised to limit the number of collections to less than 10,000 to avoid excessive service loss due to long-time startup.
  • If you enable operation protection to improve the security of your account and cloud products, two-factor authentication is required for sensitive operations. For details about how to enable operation protection, see Operation Protection in Identity and Access Management User Guide.

Restarting an Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, locate the instance and in the Operation column, choose More > Restart.

    Figure 1 Restarting an instance

    Alternatively, click the instance name and on the displayed Basic Information page, click Restart in the upper right corner of the page.

    Figure 2 Restarting an instance

  5. If you have enabled operation protection, click Start Verification in the Restart DB Instance dialog box. On the displayed page, click Send Code, enter the verification code, and click Verify. The page is closed automatically.
  6. In the displayed dialog box, click Yes.
  7. View the instance status.

    On the Instances page, the instance status is Restarting.

Restarting a Cluster Node

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, click the cluster instance name.
  5. In the Node Information area on the Basic Information page, click the dds mongos, shard, or config tab, locate a node, and in the Operation column, click Restart.

    Figure 3 Restarting a dds mongos node

  6. In the displayed dialog box, click Yes.
  7. View the node status.

    When one node status is Restarting, other nodes of the instance cannot be restarted.

Restarting a Read Replica of a Replica Set Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, click the replica set instance.
  5. In the Node Information area on the Basic Information page, click the Read replicas tab, locate the read replica to be restarted, and click More in the Operation column.

    Figure 4 Read replicas

  6. Select Restart.
  7. In the displayed dialog box, click Yes to restart the read replica.
  8. View the status of the read replica.

    When one node status is Restarting, other nodes of the instance cannot be restarted.

Forcibly Restarting an Abnormal Node

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, locate the target DB instance and click its name.
  5. In the Node Information area on the Basic Information page, click Forcibly Restart in the Operation column of the target abnormal node.

    Figure 5 Selecting an abnormal node

  6. In the displayed dialog box, click Yes to restart the abnormal node.

    Figure 6 Restarting the abnormal node

  7. View the status of the node.

    When one node status is Restarting, other nodes of the instance cannot be restarted.

Restarting Nodes in a Replica Set Instance One by One

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Databases > Document Database Service.
  4. On the Instances page, locate the replica set instance and in the Operation column, choose More > Restart.

    Figure 7 Restarting a replica set instance

    Alternatively, click the replica set instance name and on the displayed Basic Information page, click Restart in the upper right corner of the page.

    Figure 8 Restarting a replica set instance

  5. In the displayed dialog box, select Restart nodes one by one.
  6. Click Yes to restart the replica set instance nodes one by one.
  7. Check the DB instance status.

    On the Instances page, the instance status is Restarting. If nodes in a replica set instance are restarted one by one, a primary/secondary switchover is triggered.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback