[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: |
|
||||||||||||||||||||||||||||||||||||
| 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. 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
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: |
| Comment by Githook User [ 01/Dec/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| 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. |