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)