-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.0.1
-
Component/s: None
-
None
-
ALL
This feels very similar to SERVER-32521 which I filed a while back but now I'm on Atlas replica set (which was upgraded from 3.6 to 4.0) and I see every five minutes in the logs:
2018-08-31T00:09:09.665+0000 I COMMAND [LogicalSessionCacheRefresh] command config.$cmd command: createIndexes { createIndexes: "system.sessions", indexes: [ { key: { lastUse: 1 }, name: "lsidTTLIndex", expireAfterSeconds: 1800 } ], $db: "config" } numYields:0 reslen:275 locks:{ Global: { acquireCount: { r: 2, w: 2 } }, Database: { acquireCount: { w: 1, W: 1 }, acquireWaitCount: { W: 1 }, timeAcquiringMicros: { W: 464030 } }, Collection: { acquireCount: { w: 1 } } } protocol:op_msg 464ms
- duplicates
-
-
- Closed
-
- related to
-
SERVER-36961 createIndexes command should check if index already exists with weak lock
-
- Closed
-