[SERVER-35821] readConcern:snapshot transactions need a read timestamp <= WT's all_committed point Created: 26/Jun/18 Updated: 29/Oct/23 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||||||||||||||||||||||
| Sprint: | Repl 2018-07-16, Repl 2018-08-27, Repl 2018-09-10, Repl 2018-09-24 | ||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||
| Comments |
| Comment by Judah Schvimer [ 29/Jan/19 ] |
|
I've filed |
| Comment by Matthew Russotto [ 29/Jan/19 ] |
|
I think it was just missed. |
| Comment by Githook User [ 25/Sep/18 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}Message: (cherry picked from commit c46faf4672c81d4801014981669d770fc65b950e) |
| Comment by Githook User [ 14/Sep/18 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}Message: |
| Comment by Matthew Russotto [ 05/Jul/18 ] |
|
FWIW, present behavior is that if there's a pending write, it will not be read by a transaction with a read-at time after it, even if the pending write is committed at some point during that transaction. That is, snapshot behavior is preserved but relative ordering of the writes is not. |
| Comment by Spencer Brody (Inactive) [ 26/Jun/18 ] |
|
We only need to do this if the actual requested readConcern was snapshot. We don't need to do this for local or majority RC. |