-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: 5.0.25
-
Component/s: None
-
Storage Execution
-
ALL
-
Execution Team 2024-06-24, Execution Team 2024-07-22, Execution Team 2024-09-30, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-12-09, Execution Team 2024-12-23, Execution Team 2025-01-06, Execution Team 2025-02-17, Storage Execution 2025-03-03, Storage Execution 2025-03-17, Storage Execution 2025-03-31
-
(copied to CRM)
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
We set the storage stats that we want to report in curop here with the assumption that computeOperationStatisticsSinceLastCall() is called at the end of every operation. However, it is possible not to meet these conditions ( + this on previous versions) resulting in some operations not calling computeOperationStatisticsSinceLastCall(). When we eventually do call the method on a slow op we want to log, _sessionStatsAfterLastOperation can be stale and we end up reporting storage stats that include prior operations.
- is related to
-
-
- Closed
-
-
SERVER-84574 Capture additional metrics in query stats and evaluate their performance impact
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-68739 Add WiredTiger session statistic without affecting slow op statistics
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-