New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If a secondary goes down, nodes take a long time to refresh #321

Open
dblock opened this Issue Sep 28, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@dblock
Contributor

dblock commented Sep 28, 2014

We had a secondary go down, causing a heartbeat check failure in MongoDB and the following in the MongoDB logs:

Sun Sep 28 13:27:21.905 [rsHealthPoll] couldn't connect to c0.gravity.member4.mongolayer.com:27017: couldn't connect to server c0.gravity.member4.mongolayer.com:27017 

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.

@wandenberg

This comment has been minimized.

Contributor

wandenberg commented Feb 13, 2015

Hi @dblock could you check if the code on #352 fix this?
If not, let me know.

@dblock

This comment has been minimized.

Contributor

dblock commented Feb 14, 2015

We'll try to upgrade production to moped HEAD this week.

@johnnyshields

This comment has been minimized.

johnnyshields commented Feb 15, 2015

FYI I believe this is the same bug I reported on Mongoid https://github.com/mongoid/mongoid/issues/3892

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment