[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: |
| Comment by Githook User [ 18/Nov/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |