A proposal for handling users upgrading from 3.x to 3.2:
If a mongod is started without --storageEngine and the storage.bson file in the dbpath indicates mmapv1, then set the global storage engine as mmapv1. Otherwise, set the global storage engine as wiredTiger.
A proposal for handling users upgrading from 2.6 to 3.2:
If a mongod is started without --storageEngine and the local.ns file exists in the dbpath, then set the global storage engine as mmapv1. Otherwise, set the global storage engine as wiredTiger. This allows users to upgrade directly from 2.6 to 3.2, even though the storage.bson file would not exist.
- depends on
-
SERVER-18630 Replace runMongoProgram("mongod", ...) with MongoRunner.runMongod(...)
- Closed
-
SERVER-18635 transitioning_to_and_from_WT.js should test upgrading from 3.0 to 3.1.x
- Closed
-
SERVER-18673 ScopedThreads used by parallel suite do not get TestData configuration
- Closed
- is duplicated by
-
SERVER-538 SetProcessWorkingSetSizeEx for win32?
- Closed