Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-60629

Enhance Atlas API with ability to change the networkMessageCompressor values and order

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      With the completion of https://jira.mongodb.org/browse/CLOUDP-85175 Atlas users can now leverage Network Compressors of zstd, snappy, or zlib.  However, they are unable to configure the order of these compressors.  

      The order of the network compressors matter as stated in our documentation: https://docs.mongodb.com/manual/reference/configuration-options/#mongodb-setting-net.compression.compressors

      // If you specify multiple compressors, then the order in which you list the compressors matter as well as the communication initiator. For example, if mongosh specifies the following network compressors zlib,snappy and the mongod specifies snappy,zlib, messages between mongosh and mongod uses zlib.
      

      For this reason, it is important that customers and configure the Atlas Network Compressors, and change the intended order.  The current default is snappy,zstd,zlib but customers should have flexibility to configure with an order such as zstd,zlib,snappy.

      This ticket is to add this networkMessageCompressor configuration to the Atlas API.

            Assignee:
            Unassigned Unassigned
            Reporter:
            bryan.zelle@mongodb.com Bryan Zelle
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: