[SERVER-39036] Stop pinning stable timestamp behind prepared transactions Created: 16/Jan/19 Updated: 29/Oct/23 Resolved: 02/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Pavithra Vetriselvan |
| 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: | Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08 | ||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 10 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
We will no longer pin the stable timestamp behind the oldest prepare timestamp, or behind the oldest prepare timestamp of a transaction whose corresponding commit/abort oplog entries have not been majority committed. That is, we will revert |
| Comments |
| Comment by Kelsey Schubert [ 30/Jul/19 ] |
|
committed under https://github.com/mongodb/mongo/commit/e433a5aee915568cf73b05e89597903855ed1952 |
| Comment by Pavithra Vetriselvan [ 26/Feb/19 ] |
|
siyuan.zhou, I think this is fixed by suganthi.mani's work on |
| Comment by Siyuan Zhou [ 19/Feb/19 ] |
|
In Pavi's recent work for rollback, the timestamp a rollback recovered to is passed into applyCommitTransaction() to check whether a commit oplog entry has been applied or not. With Oplog Durability project, that's no longer correct, since all oplog entries after the rollback recovery timestamp have to be applied, no matter whether their commit time is greater than the rollback recovery timestamp or not. I can't find a ticket related to that work, so I'm making a note here. CC tess.avitabile. |
| Comment by Samyukta Lanka [ 07/Feb/19 ] |
|
This ticket should also address these TODOs. |