Log file Viewer

[15:57:48] <RxMcDonald> anyone?

[16:00:23] <Derick> can you not use these to $lookup again?

[16:00:29] <Derick> that's pretty much a sub query

[16:05:17] <salty-horse> hey. when upgrading a config server from SCCC to CSRS, the guide (specifically the downtime guide), keeps all 3 old config servers up while creating the 3 new replica-set based config servers. isn't 1 old config server enough? by "downtime" I'm assuming I can shut down mongos and the shards, so what is there to worry about?

[16:05:35] <salty-horse> this is the guide I'm referring to: https://docs.mongodb.com/v3.4/tutorial/upgrade-config-servers-to-replica-set-downtime/

[16:06:19] <Derick> it's probably a safety precaution

[16:11:02] <salty-horse> Derick, if I'm already working from a restored snapshot, which included a single config server that I then copied manually to create the other two, would you say it's ok to skip this precaution? (I'm testing this now)

[16:11:39] <Derick> i have not done this before, but I would therefore follow the instructions to the letter

[16:16:10] <salty-horse> will do, thanks :)

[16:16:48] <salty-horse> is there a preferred port for the replica set config servers? the old port was 27019, and since I'm starting the new rs-based ones on the same machine, I need another one

[17:02:04] <RxMcDonald> Derick: what do you mean not use these to $lookup again?

[20:02:25] <RxMcDonald> Called createIndex in a large database and it's stuck

[20:02:48] <RxMcDonald> apparently it's blocking eveything, didnt know it wasn't supported as a background operation as default