Help Center> Data Replication Service> Troubleshooting> Solutions to Failed Check Items> Database Configuration Items> Checking Whether the Maximum Number of Chunks in the Destination Database Is Sufficient

Updated on 2022-09-21 GMT+08:00

View PDF

Checking Whether the Maximum Number of Chunks in the Destination Database Is Sufficient

MongoDB Migration

**Table 1** Checking whether the maximum number of chunks in the destination database is sufficient
Check Item	Whether the maximum number of chunks in the destination database is sufficient
Description	The maximum number of chunks in the destination database is insufficient to support sharding and splitting of the source database. If the maximum number of chunks is reached, chunks are not split and the write performance is negatively affected.
Failure Cause and Handling Suggestion	Item to be confirmed: The maximum number of chunks in the destination database is insufficient to support sharding and splitting of the source database. If the maximum number of chunks is reached, chunks are not split and the write performance is negatively affected. Handling suggestion: Select a destination DB instance of higher specifications.

Parent topic: Database Configuration Items

Previous topic: Checking Whether the Source Database Schema Name Is Valid

Next topic: Checking Whether Archive Logs Are Enabled on the Source Oracle Database

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel