[SERVER-84700] minValid timestamp printed during rollbackViaRefetch can be stale Created: 09/Jan/24 Updated: 02/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shin Yee Tan | Assignee: | Vishnu Kaushik |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2024-02-05, Execution Team 2024-02-19 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
During rollback via refetch, if an exception is thrown (example) before the minValid timestamp is updated, the previous timestamp is reported which can be misleading as it is stale. |