[SERVER-54761] Add invariant that a transaction's read timestamp satisfies read concern constraints Created: 24/Feb/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Backport Requested: |
v4.4, v4.2
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
If a startTransaction comes in with an afterClusterTime, we never validate that the readTimestamp captured here actually satisfied the afterClusterTime. |