[SERVER-79256] PreImagesCollectionManager does not report "maxWallTimeMillis" when truncates are enabled Created: 24/Jul/23 Updated: 29/Oct/23 Resolved: 11/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution EMEA Team 2023-08-07, Execution EMEA Team 2023-08-21 |
| Participants: |
| Description |
|
When using unreplicated truncates, the _purgingStats.maxStartWallTimeMillis is never propagated from the stats returned from _truncateManager.truncateExpiredPreImages |
| Comments |
| Comment by Githook User [ 11/Aug/23 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |