Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.

On this page
Help Center/ Document Database Service/ FAQs/ Database Performance/ What Can I Do If a Query Error Is Reported After Data Is Written Into the DDS Cluster?

What Can I Do If a Query Error Is Reported After Data Is Written Into the DDS Cluster?

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

Symptom

Data is continuously written into the DDS cluster. After the data is written into the DDS cluster, an error is reported during query.

Example:

W SHARDING [Balancer] Failed to enforce tag ranges :: caused by :: ExceededTimeLimit: Unable to obtain shard utilization information for shard01 due to Operation timed out, request was RemoteCommand xxx -- target: 192.168.*.*:8635, db: admin, cmd:{ getShardStatistics: 1, maxTimeMS: 30000 }

Possible Cause

Data is continuously written into the storage system, causing chunk splitting timeout in the background.

Solution

This is a normal warning error and does not affect operations. You can try again later.

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback