[SERVER-60629] Enhance Atlas API with ability to change the networkMessageCompressor values and order Created: 12/Oct/21  Updated: 12/Oct/21  Resolved: 12/Oct/21

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

Type: Task Priority: Major - P3
Reporter: Bryan Zelle Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

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.



 Comments   
Comment by Bryan Zelle [ 12/Oct/21 ]

Have moved this from Server to ProdTriage

Generated at Thu Feb 08 05:50:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.