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

Mongo Shell does not accept compressors connection string argument

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.5, 4.0.0-rc1
    • Fix Version/s: 3.6.10, 4.0.5, 4.1.5
    • Component/s: Shell
    • Labels:
    • Backwards Compatibility:
      Minor Change
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6
    • Steps To Reproduce:
      Hide
      1. Start mongod with compression.
      2. Connect the mongo shell using a URI containing compressors=snappy.
      3. Run db.serverStatus and observe that network.compression.snappy.compressor.bytesIn is zero.
      4. Quit the shell
      5. Connect the mongo shell using --networkMessageCompressors=snappy.
      6. Run db.serverStatus and observe the network.compression.snappy.compressor.bytesIn is non-zero.
      Show
      Start mongod with compression. Connect the mongo shell using a URI containing compressors=snappy. Run db.serverStatus and observe that network.compression.snappy.compressor.bytesIn is zero. Quit the shell Connect the mongo shell using --networkMessageCompressors=snappy . Run db.serverStatus and observe the network.compression.snappy.compressor.bytesIn is non-zero.
    • Sprint:
      Service Arch 2018-10-22, Service Arch 2018-11-05

      Description

      When using a connection string URI with the compressors URI option, the mongo shell does not connect to the server with compressor. The mongo shell will connect with compression when the networkMessageCompressors flag is used.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tyler.kaye Tyler Kaye
              Reporter:
              kris.brandow Kristofer Brandow (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: