-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: CLI Module, Connectivity
-
None
-
5
Problem Description
Steps to Reproduce
My MongoDB Atlas cluster is configured with a network compressor value of zstd. We officially support zstd as a network compression method since v4.2 as stated in our documentation
Confirming the Atlas cluster network compression:
db._adminCommand({getCmdLineOpts: 1}).parsed.net.compression
>>> { "compressors" : "snappy,zstd,zlib" }
mongosh --version // confirming mongosh version
>>> 0.14.0
mongosh "mongodb+srv://zstd.g3mcy.mongodb.net/?compressors=zstd" --username main_user --password bryanzelle
>>> MongoParseError: zstd is not a valid compression mechanism
Expected Results
Be able to connect to my Atlas Cluster.
Org: SA-NORTHAMERICA-CENTRAL
Project: BRYAN-ZELLE
Cluster: zstd
As you can see, this same command using zlib as the compressor value works perfectly, but zstd fails:
mongosh "mongodb+srv://zstd.g3mcy.mongodb.net/?compressors=zlib" --username main_user --password bryanzelle
>>> Current Mongosh Log ID: 60c2bd2fd7c287bee22fda35
>>> Enterprise atlas-q8j1bk-shard-0 [primary]>
Actual Results
MongoParseError: zstd is not a valid compression mechanism
Additional Notes
- depends on
-
NODE-1837 Add support for Zstandard compression
- Closed
- related to
-
MONGOSH-826 MongoError: Optional module `snappy` not found. Please install it to enable snappy compression
- Closed