(DOCSP-13514) Add advanced storage and log settings (#498)

* (DOCSP-13514) Add advanced storage and log settings

Author: zach-carr

source/reference/mms-cluster-settings-file.txt

@@ -180,8 +180,8 @@ replica set member:
      - boolean
      - Flag that indicates whether the |mongos| or |mongod| instance 
        binds to all IPv4 addresses (for example, ``0.0.0.0``). If 
-       ``ipv6`` is set to ``true``, ``bindIpAll` also binds to IPv6 
-       addresses (for exmaple, ``::``). {+mcli+} accepts ] the 
+       ``ipv6`` is set to ``true``, ``bindIpAll`` also binds to IPv6 
+       addresses (for example, ``::`` ). {+mcli+} accepts the 
        following values: ``true`` or ``false``.
 
        This setting corresponds to the :manual:`net.bindIpAll 
@@ -217,12 +217,44 @@ replica set member:
        replica set configuration option.
      - no
 
+   * - ``directoryPerDB``
+     - boolean
+     - Flag that indicates whether MongoDB should use a separate directory to store data 
+       for each database. The directories are under the 
+       :setting:`storage.dbPath` directory, and each subdirectory name 
+       corresponds to the database name.
+
+       By default, ``directoryPerDB`` is ``false``.
+
+       This setting corresponds to the :setting:`storage.directoryPerDB`
+       |mongod| replica set configuration option.
+     - no
+
    * - ``hostname``
      - string
      - Name of the host to add to the replica set. This is the 
        host on which |mms| deploys the |mongod| process.
      - yes
 
+   * - ``inMemory.engineConfig.inMemorySizeGB``
+     - float
+     - Maximum amount of memory to allocate for 
+       :manual:`in-memory storage engine </core/inmemory>` data, 
+       including indexes, oplog if the :binary:`~bin.mongod` is part of 
+       replica set, replica set or sharded cluster metadata, etc.
+
+       The value can range from ``256`` MB to ``10`` TB. By default, 
+       the in-memory storage engine uses 50% of physical RAM minus 1 GB.
+
+       .. note:: Enterprise Feature
+          
+          Available for MongoDB Enterprise only.
+
+       This setting corresponds to the 
+       :setting:`storage.inMemory.engineConfig.inMemorySizeGB`
+       |mongod| replica set configuration option.
+     - no
+
    * - ``ipv6``
      - boolean
      - Flag that indicates whether the deployment supports |ipv6|.
@@ -502,6 +534,165 @@ replica set member:
        </reference/replica-configuration/#rsconf.members[n].votes>`.
      - yes
 
+   * - ``wiredTiger.engineConfig.cacheSizeGB``
+     - float
+     - Maximum size of the internal cache that WiredTiger 
+       uses for all data.
+
+       The value can range from ``0.25`` GB to ``10000`` GB. By 
+       default, the WiredTiger internal cache size is the larger of 
+       either:
+
+       - 50% of (RAM - 1 GB), or
+       - 256 MB.
+
+       Avoid increasing the WiredTiger internal cache size above its 
+       default value.
+
+       This setting corresponds to the 
+       :setting:`storage.wiredTiger.engineConfig.journalCompressor`
+       |mongod| replica set configuration option.
+     - no
+
+   * - ``wiredTiger.engineConfig.journalCompressor``
+     - string
+     - Type of compression to use to compress WiredTiger 
+       journal data.
+       
+       Available compressors are:
+   
+       - ``none``
+       
+       - :term:`snappy`
+       
+       - :term:`zlib`
+       
+       - :term:`zstd` (Available for clusters running MongoDB 4.2 and 
+         later)
+
+       By default, WiredTiger uses :term:`snappy`.
+
+       This setting corresponds to the 
+       :setting:`storage.wiredTiger.engineConfig.journalCompressor`
+       |mongod| replica set configuration option.
+     - no
+
+   * - ``wiredTiger.engineConfig.directoryForIndexes``
+     - boolean
+     - Flag that indicates whether |mongod| stores indexes and collections in 
+       separate subdirectories under the data 
+       (i.e. :setting:`storage.dbPath`) directory. Specifically, 
+       |mongod| stores the indexes in a subdirectory named ``index`` 
+       and the collection data in a subdirectory named ``collection``.
+
+       By using a symbolic link, you can specify a different location 
+       for the indexes. Specifically, when the |mongod| instance is 
+       **not** running, move the ``index`` subdirectory to a new 
+       destination and create a symbolic link named ``index`` under the 
+       data directory to the new destination.
+
+       By default ``wiredTiger.engineConfig.directoryForIndexes`` is 
+       ``false``.
+
+       This setting corresponds to the 
+       :setting:`storage.wiredTiger.engineConfig.directoryForIndexes`
+       |mongod| replica set configuration option.
+     - no
+
+   * - ``wiredTiger.engineConfig.maxCacheOverflowFileSizeGB``
+     - float
+     - .. note:: Limited version support
+          
+          This setting is only supported for clusters running MongoDB 
+          versions:
+
+          - 4.0.12 through 4.0.x, and
+
+          - 4.2.1 through 4.2.x.
+
+       Maximum size (in GB) for the "lookaside (or cache
+       overflow) table" file named :file:`WiredTigerLAS.wt`. The file no 
+       longer exists starting in MongoDB version 4.4.
+       
+       The setting can accept the following values:
+       
+       .. list-table::
+          :header-rows: 1
+          :widths: 20 80
+       
+          * - Value
+            - Description
+       
+          * - ``0``
+       
+            - The default value. If set to ``0``, the file size is
+              unbounded.
+       
+          * - number >= 0.1
+       
+            - The maximum size (in GB). If the :file:`WiredTigerLAS.wt`
+              file exceeds this size, |mongod| exits with a
+              fatal assertion. You can clear the 
+              :file:`WiredTigerLAS.wt` file and restart |mongod|.
+       
+       To change the maximum size during runtime, use the
+       :parameter:`wiredTigerMaxCacheOverflowSizeGB` parameter.
+
+       This setting corresponds to the 
+       :setting:`storage.wiredTiger.engineConfig.maxCacheOverflowFileSizeGB`
+       |mongod| replica set configuration option.
+     - no
+
+   * - ``wiredTiger.collectionConfig.blockCompressor``
+     - string
+     - Default compression for collection data. You can
+       override this on a per-collection basis when creating 
+       collections.
+       
+       Available compressors are:
+       
+       - ``none``
+       
+       - :term:`snappy`
+       
+       - :term:`zlib`
+       
+       - :term:`zstd` (Available for clusters running MongoDB 4.2 and 
+         later)
+
+       By default the compressor is :term:`snappy`.
+       
+       This setting affects all newly created collections. If you change
+       the value of this setting on an existing MongoDB deployment, all 
+       new collections will use the specified compressor. Existing 
+       collections continue to use the compressor that was specified when they 
+       were created, or the default compressor at that time.
+
+       This setting corresponds to the 
+       :setting:`storage.wiredTiger.collectionConfig.blockCompressor`
+       |mongod| replica set configuration option.
+     - no
+
+   * - ``wiredTiger.indexConfig.prefixCompression``
+     - boolean
+     - Flag that indicates whether to enable or disable :term:`prefix compression` for index data.
+   
+       If ``true``, :term:`prefix compression` is enabled for
+       index data. If ``false``, prefix compression is disabled.
+
+       By default ``wiredTiger.indexConfig.prefixCompression`` is 
+       ``true``.
+   
+       This setting affects all indexes created. If you change
+       the value of this setting on an existing MongoDB deployment, all 
+       new indexes will use prefix compression. Existing indexes
+       are not affected.
+
+       This setting corresponds to the 
+       :setting:`storage.wiredTiger.indexConfig.prefixCompression`
+       |mongod| replica set configuration option.
+     - no
+
 .. _shard-settings:
 
 Shard Settings