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

Creating Data Consistency Check Task

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-10-10 15:35:43

Overview

During data consistency check, DTS compares the table data between the source and target databases and outputs the comparison result and inconsistency details for you to determine the business cutover time. A data consistency check task is independent of the normal business in the source database or other DTS tasks.
Data consistency check tasks can be triggered automatically or created manually.
Automatic triggering: During migration task configuration, if Full check is selected for Data Consistency Check, a data consistency check task will be triggered automatically when the migration task enters the incremental sync step.
Manual creation: When the DTS task enters the incremental sync step, you can manually create one or multiple data consistency check tasks.

Triggering a data consistency check task automatically

On the Set migration options and select migration objects page of a data migration task, select Full check for Data Consistency Check. In this way, a data consistency check task will be triggered automatically when the migration task enters the incremental sync step.
Note:
In this case, the full data and all the database information will be checked by default. If you need to filter check objects, create a data consistency check task manually.

Creating a data consistency check task manually

1. Log in to the DTS console.
2. On the Data Migration page, select the target migration task and click More > Create Data Consistency Check Task in the Operation column.
3. Click Create Data Consistency Check Task.
Note:
A data consistency check task can be created only when the corresponding DTS task is in the incremental sync step. If the button is grayed out, the DTS task status does not meet the requirement; for example, the task has not entered the incremental sync step, has failed, or is terminated.

4. In the pop-up window, click Confirm.

5. After configuring the data consistency check parameters, click Start Data Comparison.
Check Object: Select All Migration Objects or Custom.
Database Information: Select Index, Shard key (if both the source and target databases are sharded clusters), or Database and table for check.
Data Check: The Row count check option compares the number of data rows in the source and target databases. The Content check option compares the data content of the source and target databases.
Sampling: In scenarios with a high data volume, extracting all the data for check may increase the load of the source database. If you select Content check, you can set an appropriate percentage based on your business conditions to extract a certain proportion of data for comparison.


Viewing the data consistency check result

1. On the migration task homepage, view whether the check result is Consistent or Inconsistent in the Last Check Result column. Click View More to enter the Verification Details page.


2. Click View to view the check result.


If the data is consistent, the result will be like:


Inconsistency check result:
Note:
For inconsistent data, you need to manually confirm the corresponding data content of the source and target databases as prompted. For more details, please refer to Common Consistency Check Issues.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック