tencent cloud

All product documents
TencentDB for MongoDB
DocumentationTencentDB for MongoDBOperation GuideData Migration GuideConsistency Check After MigrationCommon Consistency Verification Issues
Common Consistency Verification Issues
Download PDF
Last updated: 2024-10-10 15:31:46
Common Consistency Verification Issues
Last updated: 2024-10-10 15:31:46
Download PDF

Data content inconsistency

Issue
Cause analysis During a full data check, data is continuously written to the source database, and the oplog keeps being updated. The incremental data check task continuously reads the oplog from the source database. If the new oplog generated in the source database has not reached the timestamp in the target database, the data content may be inconsistent for a short period of time, which is normal.
Solution You can check the inconsistent data row by row. You can also initiate a new check task to perform another manual check. When all the incremental data is migrated to the target database, the content will be consistent.

Data row count inconsistency

Issue
Cause 1 During a full data check, data is continuously written to the source database, and the oplog keeps being updated. The incremental data check task continuously reads the oplog from the source database. If the new oplog generated in the source database has not reached the timestamp in the target database, the number of data rows may be inconsistent for a short period of time, which is normal.
Cause 2 The TencentDB for MongoDB row count check collects the row count in metadata through db.collection.estimatedDocumentCount() or db.collection.stats() for comparison, which may be inconsistent with the actual row count under specific circumstances such as unexpected instance shutdown or the presence of orphaned documents.
Solution In this case, you can use db.collection.countDocuments() to compare the row count. Note that this requires collection scanning, which may affect the performance. For more information, see db.collection.countDocuments().

Index check

Issue If you select Index for Database Info when creating a consistency check task, the indexes in the source and target databases will be compared. You may find that the content of the v and background fields in the source and target databases are inconsistent, but the check result does not indicate any inconsistency.
Cause analysis The TencentDB for MongoDB index check policy ignores the inconsistency in the v (version information) and background (creation in the background) fields, which will not be indicated in the check result.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon