[SERVER-50171] Move critical section log message Created: 07/Aug/20 Updated: 29/Oct/23 Resolved: 07/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-08-10 |
| Participants: |
| Description |
|
The time spent in waitForCollectionFlush() should not be included in the critical section duration calculations done in the new workload. This log line for end critical section should be moved to directly after the lambda containing _critSec.reset() |
| Comments |
| Comment by Githook User [ 07/Aug/20 ] |
|
Author: {'name': 'Allison Easton', 'email': 'akeaston@umich.edu', 'username': 'allisoneaston'}Message: |