Log file Viewer

[16:17:08] <Mmike> Hello, ppl. Where does mongo stores information about replicaset? I need to change replicaset configuration but without starting mongod with --replset option

[16:20:40] <Derick> it stores it in the "local" database

[19:28:54] <snooops> hi, why im not gettint the data with the query?

[19:28:56] <snooops> https://gist.github.com/snooops/6c021423db69d49f68506bcad6208f1b

[19:29:01] <snooops> getting

[19:31:53] <snooops> i edited the gist: https://gist.github.com/snooops/6c021423db69d49f68506bcad6208f1b

[19:32:14] <snooops> one solution is working, the other dont.

[19:42:24] <Derick> snooops: because one is using a string to compare with a UTCDateTime field

[19:42:27] <Derick> and that you can't do

[19:43:10] <Derick> You can do $lte: ISODate("2018-10-30"),

[19:43:14] <Derick> instead of just $lte: "2018-10-30",

[19:43:27] <snooops> yip got it, thanks ;)

[19:54:36] <snooops> is mongodb bson\Date the same as date?

[20:48:08] <Derick> there is no such class...

[22:56:22] <underguiz> hi guys, so I have a mongodb server (3.6.8) where most of the queries have a high timeAcquiringMicros (r) time (+2 seconds), even with this type of plan: planSummary: IDHACK keysExamined:1 docsExamined:1 cursorExhausted:1 numYields:0 nreturned:1

[22:56:58] <underguiz> I'm failing to figure out what might be causing this

[22:58:21] <underguiz> it's actually a replicaset, and the server having this issue is a secondary node

[23:09:45] <underguiz> here's the full lock info: locks:{ Global: { acquireCount: { r: 2 }, acquireWaitCount: { r: 1 }, timeAcquiringMicros: { r: 2052287 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } }