[SERVER-29539] Visibility issues for readAfterClusterTime at level local Created: 09/Jun/17 Updated: 06/Dec/22 Resolved: 06/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage 2017-07-31 | ||||||||
| Participants: | |||||||||
| Description |
|
When reading after a cluster time at level local, it is possible to have outstanding uncommitted transactions hide data assigned to an earlier cluster time. This is because optimes are not assigned by commit order. |