[SERVER-71145] Allow observed all_durable to move backward Created: 07/Nov/22 Updated: 29/Oct/23 Resolved: 08/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Execution Team 2022-11-14 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 5 | ||||||||||||||||
| Description |
|
The all_durable timestamp is maintained by the storage engine and may move backward. In the MongoDB integration with WT, we keep track of the highest seen all_durable and use that instead if the all_durable returned from WT is lower. This behavior was previously necessary due to ghost timestamps. Now with ghost timestamps having given up the ghost, we should be able to remove this and simply always return the all_durable that WT reports. |
| Comments |
| Comment by Githook User [ 08/Nov/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |