This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
Mark node as not down when alive connection was acquired #383
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've discovered this problem when running latest moped:master with thin server
in threaded mode (
--threaded
). We have one Mongo server and when itgoes down for a few secs, some of our app servers are unable to reconnect to
it. We see lots of log output like this:
MOPED: Retrying connection attempt 1 more time(s), nodes is [], seeds are
MOPED: Retrying connection attempt 1 more time(s), nodes is [], seeds are
MOPED: Retrying connection attempt 1 more time(s), nodes is [], seeds are