If a secondary goes down, nodes take a long time to refresh #321
We had a secondary go down, causing a heartbeat check failure in MongoDB and the following in the MongoDB logs:
This made our response time 5x slower, taking about 400ms to create a new Moped session. I didn't debug where exactly it was sitting, but I am going to imagine it's not too hard to replicate.
I would expect something a bit more efficient, IMO node rediscovery should not be blocking a request.
The text was updated successfully, but these errors were encountered: