[SERVER-18867] Remove commit/rollback logic for Changes from Storage Engine-specific RecoveryUnits Created: 08/Jun/15  Updated: 28/Jun/19  Resolved: 25/Jun/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.1.4
Fix Version/s: 4.3.1

Type: Bug Priority: Minor - P4
Reporter: Geert Bosch Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-38397 make WiredTigerRecoveryUnit::State a ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Quint 9 09/18/15, Execution Team 2019-06-17, Execution Team 2019-07-01
Participants:

 Description   

Now nested units of work are removed (SERVER-18168), there is no need for storage engine specific RecoveryUnit's to deal with the concept of registering changes for commit or rollback. So, individual Storage Engines should not need to implement this logic. One potential way to address this is to move the Changes logic into the RecoveryUnit interface directly.



 Comments   
Comment by Githook User [ 28/Jun/19 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria@mongodb.com'}

Message: SERVER-18867 Restore _getState() to registerChange invariant
Branch: master
https://github.com/mongodb/mongo/commit/562d735c3741953235b51c3f5a0a12ccc8212f76

Comment by Githook User [ 24/Jun/19 ]

Author:

{'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}

Message: SERVER-18867 Move Changes logic into RecoveryUnit
Branch: master
https://github.com/mongodb/mongo/commit/5c5832b459baa56b6bee172ee13fca97518436e2

Comment by Maria van Keulen [ 17/Jun/19 ]

It looks like SERVER-38397 makes this ticket easier, so I'm adding a dependency link.

Generated at Thu Feb 08 03:48:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.