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

User Guide

PDF
Focus Mode
Font Size
Last updated: 2024-10-10 14:58:25

Impact on the Source Database

When DTS performs full data synchronization, it consumes certain resources from the source database, which may lead to an increase in the source database's load and put additional pressure on it. If your database configuration is insufficient, it is recommended to perform data migration during off-peak hours.

Impact on the Target Database

During the migration process, DTS will use a system service account to create a table under the TencentDTSData database on the target end, using the task ID (e.g., table name dts-xxxxx). This table is used to record checkpoints, enabling checkpoint restart in case of task interruption.

Migration Architecture

1. Sharded Migration Related Notes:
1.1 Before a sharded cluster is migrated, it is recommended to clean up orphaned documents in the source cluster in advance. Otherwise, data inconsistency issues may arise after migration. For instructions on how to clean up orphaned documents, see the MongoDB official documentation cleanupOrphaned.
1.2 During a sharded migration, do not enable sharding on the source databases and tables being migrated. This is to prevent discrepancies in data distribution between the source and target databases. If sharding is enabled on the source during migration, check the sharding status on the target. If sharding is not enabled on the target, you will need to manually enable it. For detailed instructions on how to enable sharding, see the MongoDB official documentation on Shard a Collection.
1.3 If the source is a TencentDB for MongoDB 3.2 sharded cluster, all shard keys will be treated as hashed shard keys by default during migration. If you want to use range shard keys on the target, create the range shard keys on the target database in advance before the data migration is started.
2. Since a single node does not have an Oplog, incremental migration is not supported when the self-hosted instance is a single node.

Notes

1. Do not perform the following operations during migration, as they may cause the migration task to fail.
Do not modify or delete user information (including usernames, passwords, and permissions) or port numbers in the source or target databases.
Do not perform Oplog clearance operations on the source database.
During the data migration, do not delete the TencentDTSData database on the target database.
2. Be cautious when you operate on the target database during the data migration to avoid data inconsistencies.

Help and Support

Was this page helpful?

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

Feedback