The checkMetadataConsistency command sent in the background by the MetadataConsistencyChecker hook fails with a LockBusy error when a DDL lock acquisition times out (300 sec).
This error started rising more often after SERVER-85441, where we started executing moveCollection on those suites running with the balancer in the background. The moveCollection command is a reshardCollection wrapper and can take longer than 5min.
- causes
-
SERVER-89175 checkMetadataConsistency hook silently swallow comamnd errors
-
- Closed
-
- is related to
-
SERVER-89841 Investigate DDL LockBusy errors in config transition suite tests
-
- Closed
-