[SERVER-39870] WTKVEngine::setOldestFromStable must not choose a time earlier than the initialDataTimestamp Created: 27/Feb/19 Updated: 29/Oct/23 Resolved: 11/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| 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: | Storage NYC 2019-04-08, Storage NYC 2019-04-22 |
| Participants: |
| Description |
|
The initialDataTimestamp is the earliest time the system knows the data to be consistent. setOldestTimestampFromStable will intentionally lag the oldest timestamp a few seconds behind the stable timestamp to provide a window for reads to get in. At startup, the initialDataTimestamp will be set to the checkpoint timestamp. The system has no history before this time. However, setOldestFromStable will communicate an earlier oldest_timestamp to WiredTiger. This means a transaction with a read_timestamp can come in that WT will allow, but does not have the history to correctly satisfy. |
| Comments |
| Comment by Githook User [ 11/Apr/19 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: |
| Comment by Suganthi Mani [ 28/Mar/19 ] |
|
As a part of |
| Comment by Githook User [ 28/Mar/19 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: Revert " This reverts commit ef38b62f0de257cfa0c5a2940c67949b7402079b. |
| Comment by Githook User [ 28/Mar/19 ] |
|
Author: {'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}Message: |