Mongo update to v4.4.8

Working with Data
#1

After updating mongo to version 4.4.8, there are a lot of errors in the log files

{“t”:{"$date":“2022-01-31T14:08:13.591+02:00”},“s”:“I”, “c”:“COMMAND”, “id”:51803, “ctx”:“conn11144”,“msg”:“Slow query”,“attr”:{“type”:“command”,“ns”:“Viss_DAIRM2.auditLogEntries”,“command”:{“insert”:“auditLogEntries”,“ordered”:true,“bypassDocumentValidation”:false,“writeConcern”:{“w”:“majority”,“j”:true},“txnNumber”:27,"$db":“Viss_DAIRM2”,“lsid”:{“id”:{"$uuid":“3b5d4fa2-fa00-4c5b-afd3-0b0a0afb0191”}},"$clusterTime":{“clusterTime”:{"$timestamp":{“t”:1643630891,“i”:6}},“signature”:{“hash”:{"$binary":{“base64”:“AAAAAAAAAAAAAAAAAAAAAAAAAAA=”,“subType”:“0”}},“keyId”:0}}},“ninserted”:1,“keysInserted”:3,“numYields”:0,“reslen”:230,“locks”:{“ParallelBatchWriterMode”:{“acquireCount”:{“r”:2}},“ReplicationStateTransition”:{“acquireCount”:{“w”:3}},“Global”:{“acquireCount”:{“w”:2}},“Database”:{“acquireCount”:{“w”:2}},“Collection”:{“acquireCount”:{“w”:2}},“Mutex”:{“acquireCount”:{“r”:2}}},“flowControl”:{“acquireCount”:1,“timeAcquiringMicros”:1},“writeConcern”:{“w”:“majority”,“j”:true,“wtimeout”:0,“provenance”:“clientSupplied”},“storage”:{“data”:{“bytesRead”:8461,“timeReadingMicros”:46369}},“protocol”:“op_msg”,“durationMillis”:100}}

Maybe someone faced the same problem and know the solution?
Thanks!

#2

Hi @Alex_Savelev ,

This is not an error but a log line that informa some operations are crossing the 100ms logging threshold.

Its normal. If you feel performance degradation you need to investigate this performance of your cluster.

I recommend going to the latest 4.4.11 release as it has many significant fixes some are critical advisory.

Consider reading the following blogs as well

If not setisfied please contact MongoDB support.

Thanks
Pavel

#3

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.