Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
Description
----------------------------
Original Description
Description:
Both snappy and zlib are now supported by default. This will need to be updated (https://docs.mongodb.com/manual/reference/configuration-options/#net.compression.compressors). The server still prefers snappy by default, but will accept zlib compression without additional configuration.
Engineering Ticket Description:
Many drivers only support zlib compression, as snappy is not available as part of their core language libraries. The server should default to enabling both snappy and zlib, so users can seamlessly use compression once they enable it in a driver without custom server configuration.
----------------------------
Description
Scope of changes (files that need work and how much)
- source/includes/options-mongos.yaml
- source/includes/options-conf.yaml
- source/includes/fact-networkMessageCompressors.rst
- source/includes/options-mongo.yaml
- source/includes/options-mongod.yaml
- source/release-notes/4.2.txt
Impact to other docs outside of this product
MVP (work and date?)
Resources (e.g. Scope Docs, Invision)
Attachments
Issue Links
- documents
-
SERVER-36074 networkMessageCompressors should default to both snappy and zlib
-
- Closed
-
- is related to
-
DOCS-12250 Pre-4.2 --networkMessageCompressors default is incorrect
-
- Closed
-
-
RUBY-1216 Add support for reading and writing OP_COMPRESSED
-
- Closed
-