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
OneAccess
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

Rebooting a DB Instance or Node

Updated on 2025-02-12 GMT+08:00

Scenarios

You may need to reboot a DB instance or node for maintenance purposes. For example, after modifying some parameters, you may need to reboot your instance to apply the modifications. You may need to reboot a node to resolve database connection issues.

Rebooting a DB Instance

NOTICE:
  • If the DB instance status is Abnormal, the reboot may fail.
  • To shorten the time required, reduce database activities during the reboot to reduce rollback of transit transactions.
  • Rebooting a DB instance will interrupt services briefly. During this period, the instance status is Rebooting.
  • A DB instance will be unavailable when it is being rebooted. Rebooting a DB instance will clear the cached memory in it. To prevent traffic congestion during peak hours, you are advised to reboot the DB instance during off-peak hours.
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, locate the instance you want to reboot and choose More > Reboot in the Operation column.

    Alternatively, click the instance name to go to the Basic Information page. Click Reboot in the upper right corner of the page.

    The read replicas are also rebooted.

  5. If you have enabled operation protection, click Start Verification in the displayed dialog box. On the displayed page, click Send Code, enter the obtained verification code, and click Verify to close the page.

    For details about how to enable operation protection, see Identity and Access Management User Guide.

  6. In the Reboot DB Instance dialog box, set Scheduled Time.

    Figure 1 Rebooting a DB instance
    Table 1 Rebooting a DB instance

    Parameter

    Description

    Scheduled Time

    You can reboot a DB instance immediately or during the maintenance window.

    • Immediate: The DB instance will be rebooted immediately.
    • During maintenance window: The DB instance will be rebooted during a maintenance window.

      The maintenance window is 02:00–06:00 by default and you can change it as required. Changing the maintenance window will not affect the timing that has already been scheduled.

      A reboot task configured during a current maintenance window will not be executed until the next maintenance window.

  7. Click OK.
  8. View the reboot progress on the Task Center page. If the task status becomes Completed and the instance status becomes Available, the DB instance has been rebooted successfully.

Rebooting a Node

NOTICE:
  • Nodes in the Abnormal state can be rebooted.
  • To shorten the time required, reduce database activities during the reboot to reduce rollback of transit transactions.
  • Rebooting a node will interrupt services briefly. During this period, the node status is Rebooting node.
  • A node will be unavailable when it is being rebooted. You are advised to reboot the node during off-peak hours and ensure that your applications support automatic reconnection.
  • If a parameter of your DB instance is modified, you need to first reboot the DB instance to apply the modification, and then reboot a node of the DB instance.
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, click the instance name to go to the Basic Information page.
  5. In the Node List area, select the target node and click Reboot in the Operation column.
  6. If you have enabled operation protection, click Start Verification in the displayed dialog box. On the displayed page, click Send Code, enter the obtained verification code, and click Verify to close the page.

    For details about how to enable operation protection, see Identity and Access Management User Guide.

  7. In the displayed dialog box, set Scheduled Time.

    Table 2 Rebooting a node

    Parameter

    Description

    Scheduled Time

    You can reboot a node immediately or during the maintenance window.

    • Immediate: The node will be rebooted immediately.
    • During maintenance window: The node will be rebooted during a maintenance window.

      The maintenance window is 02:00–06:00 by default and you can change it as required. Changing the maintenance window will not affect the timing that has already been scheduled.

      A reboot task configured during a current maintenance window will not be executed until the next maintenance window.

  8. Click Yes.
  9. View the reboot progress on the Task Center page. If the task status becomes Completed and the node status becomes Available, the node has been rebooted successfully.

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