[SERVER-37722] Quiet mode does not suppress connection end events Created: 24/Oct/18  Updated: 29/Oct/23  Resolved: 20/Dec/18

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 3.6.8, 4.0.3
Fix Version/s: 3.6.12, 4.0.8, 4.1.7

Type: Bug Priority: Major - P3
Reporter: John Murphy Assignee: Jonathan Ma
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2018-12-19-15-11-17-957.png    
Issue Links:
Backports
Related
related to SERVER-29109 Client metadata log message verbosity... Open
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: Service Arch 2018-12-17, Service Arch 2018-12-31
Participants:
Case:

 Description   

Part of the work done in SERVER-30136 under this commit did not add the check for !quiet. The result is that we log connection end events even when they should be suppressed.



 Comments   
Comment by Githook User [ 22/Mar/19 ]

Author:

{'email': 'thejonathanma@gmail.com', 'name': 'Jonathan', 'username': 'thejonathanma'}

Message: SERVER-37722 Check for quiet flag when logging connection end message
Branch: v4.0
https://github.com/mongodb/mongo/commit/5bf7bd3ba234b851d7563bbcb799f748ee4dfc47

Comment by Githook User [ 22/Mar/19 ]

Author:

{'email': 'thejonathanma@gmail.com', 'name': 'Jonathan', 'username': 'thejonathanma'}

Message: SERVER-37722 Check for quiet flag when logging connection end message
Branch: v3.6
https://github.com/mongodb/mongo/commit/7861aff0e2befcab400a9cd5a6ad59a38e6a8bee

Comment by Benjamin Caimano (Inactive) [ 21/Dec/18 ]

I've requested backports for your release and the one before it. This will mean you'll be able to just apt-get install --only-upgrade when we release a new 4.0.x patch.

Comment by Julius Sakalys [ 21/Dec/18 ]

Thank you Ben, we're on 4.0.<something>. So would that mean that we will be able to stay on 4.1 and have the issue fixed?

Comment by Benjamin Caimano (Inactive) [ 21/Dec/18 ]

sakalys, this fix is targeted for the 4.1.7 release of MongoDB. I'd expect that release to become available in the new year. When that happens, the 4.1 list will automatically release that patch release. Do you happen to know which major/minor version you are currently using? This particular fix seems possible to backport to 4.0 and/or 3.6.

Comment by Julius Sakalys [ 21/Dec/18 ]

Hi, thank you for the commit. As I'm not very familiar on how do open source projects work, I was wondering. What should happen, in order for this fix to get into production builds, and end-up on say mongodb ubuntu repositories?

Comment by Githook User [ 20/Dec/18 ]

Author:

{'username': 'thejonathanma', 'email': 'thejonathanma@gmail.com', 'name': 'Jonathan'}

Message: SERVER-37722 Check for quiet flag when logging connection end message
Branch: master
https://github.com/mongodb/mongo/commit/a7bf3ca5bbf09d5358613c47f19ddfa0d63552c0

Generated at Thu Feb 08 04:46:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.