The cluster version of the checkMetadataConsistency command will make a cursor on each shard and the config server, which get established together via establishCursors. That helper will send the same operationKey with every request, which must be unique per process, but when the config server is also a shard, we send the same operationKey to it twice, which fails the second command to arrive with BadValue.
- duplicates
-
SERVER-74534 checkMetadataConsistency not working with co-located configsvr
-
- Closed
-
- is depended on by
-
SERVER-75164 Verify behaviour of CheckMetadataConsistencyCmd with catalog shard.
-
- Closed
-