
OPERATIONAL DEFECT DATABASE
...

...
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
nestor.urquiza@gmail.com commented on Wed, 14 Apr 2021 18:02:39 +0000: ... | grep -v 'I NETWORK'
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.