-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Labels:None
Validate collection-specific options at create time for all registered storage engines, regardless of the current storage engine in use. This is to ensure that replica sets with mixed storage engines work properly.
At this time, we will not be supporting different storage engine options for the same storage engine, for a given collection, on different replicas in the same replica set.
Original description:
It would be nice to allow different storage engine options for the same collections on different replicas in the same replica set.
This would facilitate testing different storage options without having to build new replicas nor change the default storage options for all collection on the node.
Example
For example the 3 node replica set might have the following settings to test the best storage options.
| node | collection | options |
|---|---|---|
| 1 | users | wiredtiger, lsm, direct_io |
| 2 | users | wiredtiger, btree, snappy compression |
| 3 | users | wiredtiger, lsm, zip compression |
This would be independent of the default options which could be none of those options, like wiredtiger-lsm-no-compression.
- is depended on by
-
CSHARP-1108 Add support for storage options to CreateIndex and CreateCollection
-
- Closed
-
-
-
- Closed
-
- is documented by
-
DOCS-4477 Document createCollection and createIndex storage engine option use
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-16135 WT Storage engine options should be restricted
-
- Closed
-