[SERVER-30281] Properly clear in-memory transaction table state after rollback Created: 24/Jul/17  Updated: 30/Oct/23  Resolved: 03/Aug/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.12

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-37811 Replication rollback invalidates all ... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-08-21
Participants:

 Description   

After a rollback, there needs to be logic in the session catalog to handle entries in the in-memory session transaction table that are not in state kAvailable. This applies to all rollback algorithms.



 Comments   
Comment by Githook User [ 10/Aug/17 ]

Author:

{'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow'}

Message: SERVER-30281 Force sessions to reload after rollback
Branch: master
https://github.com/mongodb/mongo/commit/045ae4aa7e54ccfdc229a22f94fdead015ece8e6

Comment by Jack Mulrow [ 25/Jul/17 ]

Updated the description to clarify that this must be done after all rollback algorithms.

Comment by Judah Schvimer [ 25/Jul/17 ]

Which rollback algorithm is this referring to? Rollback via refetch (3.4 style with UUIDs) or Rollback to a Checkpoint?

Generated at Thu Feb 08 04:23:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.