-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
In certain tests where transactions are prepared, dbcheck may be blocked from progressing. Issuing multiple dbcheck commands could exhaust all storage read tickets, leading to a deadlock situation where the JavaScript test cannot proceed. To prevent this, we should avoid starting a new dbcheck while the previous one is still running. Additionally, with the implementation of SERVER-79918, we can now wait specifically for the started dbcheck to complete before initiating another one.
- is depended on by
-
SERVER-81158 Enable disabled test because of dbcheck hook in replica sets passthrough suites
- Closed
- related to
-
SERVER-79918 Add ns and uuid to dbCheck start/stop health log entries
- Closed