-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
Sharding EMEA 2023-07-24
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The string printed in a logline error for a RESOURCE_DDL_DATABASE lock is the collection name instead of the database name.
That's an example of a logline where a lock acquisition for a DDL Database lock failed:
[fsm_workload_test:random_DDL_setFCV_operations:CheckMetadataConsistencyInBackground] "errmsg" : "Failed to acquire DDL lock for 'random_DDL_setFCV_operations_DB_1' in mode S after 300000 ms that is currently locked by '{\"{ operation: \"{ namespace: \"random_DDL_setFCV_operations_DB_1.sharded_coll_1\", operationType: \"renameCollection_V2\" }\", lock mode: \"IX\" }\", \"{ operation: \"{ namespace: \"random_DDL_setFCV_operations_DB_1.sharded_coll_1\", operationType: \"dropCollection_V2\" }\", lock mode: \"IX\" }\", \"{ operation: \"{ namespace: \"random_DDL_setFCV_operations_DB_1.sharded_coll_0\", operationType: \"createCollection_V3\" }\", lock mode: \"IX\" }\"}'",