[SERVER-47971] Awaitable isMaster commands are logged as "Slow query" Created: 05/May/20  Updated: 05/May/20  Resolved: 05/May/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.0-rc3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Shane Harvey Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-47267 Exhaust isMaster replies are logged a... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

I'm running 4.4.0-rc3 and noticed that all awaitable isMaster requests are logged as a "Slow query".

Here's an example:

{"t":{"$date":"2020-05-05T14:40:50.199-07:00"},"s":"I", "c":"COMMAND", "id":51803,  "ctx":"conn8","msg":"Slow query","attr":{"type":"command","ns":"admin.$cmd","command":{"ismaster":1,"topologyVersion":{"processId":{"$oid":"5eb1dd1acb440330e9a8dd24"},"counter":0},"maxAwaitTimeMS":10000,"$db":"admin","$readPreference":{"mode":"primary"}},"numYields":0,"reslen":304,"locks":{},"protocol":"op_msg","durationMillis":9999}}

I propose that we suppress these log messages for awaitable isMaster otherwise the log will be flooded.



 Comments   
Comment by Shane Harvey [ 05/May/20 ]

This was fixed in SERVER-47267.

Generated at Thu Feb 08 05:15:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.