Comment 1 for bug 1886498

From the logs it looks like mongo struggled to get resources from the machine. It took 8.5seconds to acquire a lock and Juju really struggled to recover.

------

 Jul 6 12:51:32 juju-4da59b22-9710-4e69-840a-be49ee864a97-machine-0 mongod.37017[16302]: [ftdc] serverStatus was very slow: { after basic: 0, after asserts: 0, after connections: 0, after extra_info: 0, after globalLock: 0, after locks: 0, after network: 0, after opcounters: 0, after opcountersRepl: 0, after repl: 0, after security: 0, after storageEngine: 0, after tcmalloc: 0, after wiredTiger: 1010, at end: 1010 }
    Jul 6 12:51:39 juju-4da59b22-9710-4e69-840a-be49ee864a97-machine-0 mongod.37017[16302]: [conn188253] command admin.system.users command: saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx" } keyUpdates:0 writeConflicts:0 numYields:0 reslen:155 locks:{ Global: { acquireCount: { r: 2 }, acquireWaitCount: { r: 1 }, timeAcquiringMicros: { r: 8443463 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 8455ms