tencent cloud

TencentDB for MongoDB

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Strengths
Use Cases
Cluster Architecture
Product Specifications
Features
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
MongoDB Pricing
Billing Formula
Payment Overdue
Backup Space Billing
Configuration Adjustment Billing
Getting Started
Quickly Creating an Instance
Connecting to a TencentDB for MongoDB Instance
Reading/Writing Database
Operation Guide
Access Management
Instance Management
Node Management
Version Upgrade
Network Configuration
Monitoring
Backup and Rollback
Database Audit
Data Security
SSL Authentication
Log Management
Database Management
Multi-AZ Deployment
Disaster Recovery/Read-Only Instances
Parameter Configuration
Recycle Bin
Task Management
Performance Optimization
Data Migration Guide
Practical Tutorial
Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
Troubleshooting Mongos Load Imbalance in Sharded Cluster
Considerations for Using Shard Clusters
Sample of Reading and Writing Data in MongoDB Instance
Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
Troubleshooting MongoDB Connection Failures
Shard Removal Task: Guide for Confirming the Progress and Troubleshooting Issues
Performance Fine-Tuning
Ops and Development Guide
Development Specifications
Command Support in Sharded Cluster v3.2
Command Support in v3.6
Development Ops
Troubleshooting
Increased Slow Queries
Number of Connections Exceeding Limit
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Backup APIs
Account APIs
Other APIs
Task APIs
Introduction
Data Types
Error Codes
Instance Connection
Shell Connection Sample
PHP Connection Sample
Node.js Connection Sample
Java Connection Sample
Python Connection Sample
Python Read/Write Sample
Go Connection Sample
PHP Reconnection Sample
Product Performance
Test Environment
Test Method
Test Result
FAQs
Cost
Features
Sharded Cluster
Instance
Rollback and Backup
Connection
Data Migration
Others
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Changing Instance AZ

PDF
Focus Mode
Font Size
Last updated: 2024-04-02 16:42:38

Overview

During regular maintenance, you can place your TencentDB for MongoDB and CVM instances in the same AZ to lower the network latency. TencentDB for MongoDB multi-AZ instances support free AZ switch, and single-AZ instances can be upgraded to multi-AZ instances.

Billing Overview

Changes to the AZ doesn't affect instance billing.

Note

‌Changes to the AZ may lead to primary-secondary switch and a momentary disconnection of about 10 seconds. It is advisable to make these changes during off-peak hours of your business.

‌Instructions

All attributes, specifications, and connection addresses of the instance will stay unchanged after AZ modification. However, the private IP of the database will change after network switch, so you need to reconnect to the instance.

Prerequisites

You have created a TencentDB for MongoDB instance. For more information, see Creating TencentDB for MongoDB Instance.
The instance is in Running status.
The target AZ and the current instance AZ are in the same region.

Directions

2. In the MongoDB drop-down list on the left sidebar, select Replica Set Instance or Sharded Cluster Instance. The directions for the two types of instances are similar.
3. Above the Instance List on the right, select the region.
4. In the instance list, find the target instance.
5. Click the instance ID to enter the Instance Details page.
6. On the Instance Details page, click Change AZs next to Region.

7. In the Change AZs window, read the notes on AZ modification. For a multi-AZ deployed instance, configure different AZs for the primary and secondary nodes respectively. For a single-AZ deployed instance, configure the same AZ for both the primary and secondary nodes.

Note:
Changes to the AZ may lead to primary-secondary switch and a momentary disconnection of about 10 seconds. It is advisable to make these changes during off-peak hours of your business.
8. Select the time for executing the AZ switch task next to Switch Time. You can click Learn more about switch time and change the instance maintenance period to the off-peak hours of your business. For detailed directions, see Setting Instance Maintenance Period.
Note:
If you have selected During maintenance period, do not select Upon modification completion to immediately execute the task before the configured maintenance period; otherwise, a program exception will occur. An initiated task cannot be stopped manually. To stop it, submit a ticket for application.
Upon modification completion: The task will be executed immediately after the configuration is completed.
During maintenance period: The task will be executed during the maintenance period.
9. Confirm Total Fees, click OK to enter the order page, check the order, click Submit Order, and make the payment to complete the operation.The instance status becomes Changing AZ. Wait for the task to be completed, and you can see that the AZ has been changed.

Subsequent operations

After changing the AZ, switch the VPC subnet to avoid a high access latency. For detailed directions, see Switching Instance Network.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback