[SERVER-33433] Rebuild in-memory Session state for committed transactions from disk when the session is first checked out Created: 21/Feb/18 Updated: 29/Oct/23 Resolved: 12/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Siyuan Zhou |
| 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 2018-04-09, Repl 2018-04-23 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Most of the machinery for this is already in place, I believe the only thing we'll have to do is handle when the txn table points to an applyOps oplog entry. Since we don't support retrying anything other than the 'commitTransaction' command, I think we'll be able to get away with just remembering that the transaction is committed, and won't actually have to parse out any information from the actual applyOps oplog entry. |
| Comments |
| Comment by Githook User [ 12/Apr/18 ] |
|
Author: {'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou', 'username': 'visualzhou'}Message: |