[SERVER-66192] Readers of the count / dataSize derived metadata should implicitly apply any available queued change Deltas before returning the latest value Created: 03/May/22 Updated: 06/Dec/22 Resolved: 01/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | DM-M1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
When a reader wants to know the latest count/dataSize value, we should first apply any unapplied Deltas before returning the latest value to the caller. Not sure whether it's reasonable to fetch the all_durable timestamp from WT every user read. It might be. Also could consider whether to use other in-memory system timestamps – maybe even the oplogReadTimestamp. |