[SERVER-16135] WT Storage engine options should be restricted Created: 13/Nov/14  Updated: 11/Aug/18  Resolved: 16/Dec/14

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

Type: Bug Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Eric Milkie
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16313 Whitelist storage engine options for ... Closed
Related
is related to SERVER-16069 Input validation on the arguments to ... Closed
is related to SERVER-16137 Validate collection options for all r... Closed
Tested
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Left side is MongoDB option name; -> right side is equivalent WiredTiger configuration option.

Options for --wiredTigerEngineConfig

cacheSizeMB: number -> cache_size=number MB
checkpointPeriodSecs: number -> checkpoint=(wait=number)
checkpointSizeBytes: number -> checkpoint=(log_size=number)
statisticsLogPeriodSecs: number -> statistics_log=(wait=number)

Options for --wiredTigerCollectionConfig, --wiredTigerIndexConfig

compression: compressor -> block_compressor=compressor, compressor=\{snappy, zlib, none\}
maxLeafPageSizeKB: number -> leaf_page_max=number KB
overflowSizeBytes: number -> leaf_item_max=number
maxPageMemorySizeKB: number -> memory_page_max=number
prefixCompression: boolean -> prefix_compression=boolean   (default on for indexes)

These options will be validated regardless of the current storage engine; this is to make mixed storage-engine replica sets work.


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