[SERVER-46297] Make all primary durable timestamp updates go through the JournalListener Created: 21/Feb/20 Updated: 29/Oct/23 Resolved: 21/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| 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 2020-02-24 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
waitForWriteConcern is sometimes setting the last durable timestamp manually, as well as implicitly by calling into the storage engine for durability. These should be consolidated for ease of understanding, because the current state is confusing; and must be done in order to pick up the correct timestamp in getToken for setting the durable timestamp. |
| Comments |
| Comment by Githook User [ 22/Feb/20 ] |
|
Author: {'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}Message: |