-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Diagnostics
-
None
-
Fully Compatible
-
Execution Team 2019-07-01
-
(copied to CRM)
The error message when a transaction statement is unable to acquire a lock within the timeout is cryptic, making it difficult to identify the conflicting operation:
Unable to acquire lock '{7817449386782089629: Database, 899920359141007773}'
Would it be possible to include more information that could help pinpoint the cause of the conflict, for example
- conflicting database or collection name
- connection number of client holding the lock
- operation id holding the lock
- name of operation holding the lock
- depends on
-
SERVER-39902 lockInfo should use UUIDCatalog to map resourceIds to collection names
- Closed
- related to
-
SERVER-39984 Log all failed transaction statements
- Closed
-
SERVER-40915 Show view namespaces in the LockManager's ResourceId::toString() function
- Closed