[SERVER-61552] Change of storage parameters for storage engine re-init must occur after shutdown Created: 16/Nov/21  Updated: 29/Oct/23  Resolved: 18/Nov/21

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Replication 2021-11-29
Participants:

 Description   

The current method of restarting storage with different parameters is to change storageGlobalParams and call reinitializeStorageEngine. This usually works, but unfortunately if WiredTiger decides to do a file version downgrade during shutdown and the Encrypted Storage Engine is enabled, the new (wrong) storageGlobalParams will be used during the file version downgrade. This can be fixed by providing a callback to reinitializeStorageEngine which can change the parameters after the old engine is shut down.

Additionally, the Encrypted Storage Engine must re-initialize with the new directory when storage changes (this bug was masked by the other)



 Comments   
Comment by Githook User [ 18/Nov/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-61552 Change of storage parameters for storage engine re-init must occur after shutdown
Branch: master
https://github.com/mongodb/mongo/commit/f5e03f7e0cbc6bf360c3a7e1a299fe0b2ad41a12

Comment by Githook User [ 18/Nov/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-61552 Ensure ESE encryption manager is re-initialized after storage change.
Update FileCopyBasedInitialSyncer storage change API use.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/94be41bf8260c878b3b423286273192802594433

Generated at Thu Feb 08 05:52:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.