-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v5.3, v5.2, v5.0
-
Sharding EMEA 2022-03-21, Sharding EMEA 2022-04-04
This error message assumes that if the critical section is held is because there is a migration, but there are other DDL ops that also acquire it.
We could write something in the line of "The critical section for $nss is acquired with reason $reason", where $nss is the namespace of the collection and $reason is obtained from the critical section object.