mongo --quiet does not silence initial connection messages

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.3
    • Component/s: Shell
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When using the --quiet option, the mongo shell still writes initial connection messages to stdout, when connecting via a replica set URL. These messages should be completely suppressed when the --quiet option is used, and even when they are not suppressed, they should be written to stderr rather than stdout.

      $ mongo --quiet "mongodb://localhost:27017/?replicaSet=rsx" --eval "print('test')"
2018-02-28T20:52:31.450+0000 I NETWORK  [thread1] Starting new replica set monitor for rsx/localhost:27017
2018-02-28T20:52:31.451+0000 I NETWORK  [thread1] Successfully connected to localhost:27017 (1 connections now open to localhost:27017 with a 5 second timeout)
2018-02-28T20:52:31.451+0000 I NETWORK  [thread1] changing hosts to rsx/amz-play:27017 from rsx/localhost:27017
2018-02-28T20:52:31.451+0000 I NETWORK  [thread1] Successfully connected to amz-play:27017 (1 connections now open to amz-play:27017 with a 5 second timeout)
test

              Assignee:
              DO NOT USE - Backlog - Platform Team
              Reporter:
              Andre Spiegel
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: