-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
v8.0, v7.0, v6.0
-
Execution Team 2024-05-27, Execution Team 2024-06-10
It seems dbStats may take a long time to execute, if there are many collections to iterate through. dbStats uses the forEachCollectionFromDb helper function, which does not appear to check for interrupts periodically.
As a result, it seems possible for a primary to step down, attempt to kill user operations, and wait to obtain RSTL, but dbStats would continue to execute through every collection. This can cause RSTL timeouts to occur on state transitions.
To help prevent this, we should consider checking for interrupts, perhaps within the dbStats code or within forEachCollectionFromDb.
- mentioned in
-
Page Loading...