Check Details
Check requirement: When the target is a sharded instance, the shard key can be preset on the target side. If the shard key of the target table is not consistent with that of the source table, a warning will be sent. The warning does not block the continuation of the task but may impact the business. Users should assess the impact and decide whether to ignore the warning.
Business impact: In scenarios where shard keys are inconsistent, the synchronization task may fail.
Fixing Method
If the shard key is preset for the target table, see the following command to perform shard operations on the source table.
sh.shardCollection("<database>.<collection>", { <shard key> : "hashed" } , false, {numInitialChunks: Number of preset chunks})
Execute the check task again.