-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
0
As seen in https://jira.mongodb.org/browse/BF-34796, it is possible that a refresh for the database can block the acquisition of a collection lock needed to execute writes. This is a transient error and the lock timeout must be increased (using the maxTransactionLockRequestTimeoutMillis parameter) in the txn_commit_optimizations_for_read_only_shards.js test.