CheckMetadataConsistency command is correctly setting snapshot read concern when reading chunks from config.chunks but since we are using the localCatalogClient (DBDirect client) the read concern provided in the command gets ignored.
Possible solution are:
- use the normal CatalogClient, this will use remote command execution path that will honor the provided read concern
- Set the read concern on the operation context before to invoking the DBDirectClient and reset once we reutrn from the call
- We could also use an alternative client reagion so that we won't need to patch up the original operation context.
- causes
-
SERVER-86278 Investigate discrepancy between ShardLocal and ShardRemote aggregations
- Backlog
- is caused by
-
SERVER-75490 Use kSnapshotReadConcern when getting chunks from config server at checkMetadataConsistency
- Closed