[SERVER-16137] Validate collection options for all registered storage engines Created: 13/Nov/14  Updated: 17/May/19  Resolved: 02/Dec/14

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 2.8.0-rc2

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by CSHARP-1108 Add support for storage options to Cr... Closed
is depended on by DRIVERS-195 Support new storage engine options fo... Closed
Documented
is documented by DOCS-4477 Document createCollection and createI... Closed
Related
related to SERVER-16135 WT Storage engine options should be r... Closed
is related to SERVER-16233 add support for storage options to cr... Closed
Tested
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 02/Dec/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-16137 correct comment
Branch: master
https://github.com/mongodb/mongo/commit/9872c67dafc6d1d5be312b97a74ee0d0d6640c3e

Comment by Githook User [ 01/Dec/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-16137 validate collection storage options for all storage engines
Branch: master
https://github.com/mongodb/mongo/commit/10f463fcf5c57b16b8d6f0d2e007efd46f4d2e70

Comment by Eric Milkie [ 19/Nov/14 ]

Addendum: Note that the same caveats for collection storage options will apply to index storage options as well.

Comment by Eric Milkie [ 19/Nov/14 ]

For rc2, we will validate collection storage options for wiredtiger regardless of the current active storage engine. We will restrict storage options to the following: lsm/btree, zip/snappy/no compression. A collection can have only one set of storage options per storage engine, across a replica set.
Mixed version replsets with 2.6 will not be supported when using collection storage options.
There will be no provision to change a preexisting collection's storage engine options in 2.8.

Generated at Thu Feb 08 03:40:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.