Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Connection ip issues #337

Merged
merged 3 commits into from
Jan 2, 2015
Merged

Connection ip issues #337

merged 3 commits into from
Jan 2, 2015

Conversation

durran
Copy link
Member

@durran durran commented Dec 15, 2014

Attempting to resolve #336 and #333

@durran
Copy link
Member Author

durran commented Jan 2, 2015

@arthurnn The testing from this issue looks good... https://jira.mongodb.org/browse/CS-15755 I've merged in - are you cool with doing a point release?

durran added a commit that referenced this pull request Jan 2, 2015
@durran durran merged commit 84618a9 into master Jan 2, 2015
@durran durran deleted the connection-ip-issues branch January 2, 2015 17:57
@arthurnn
Copy link
Contributor

arthurnn commented Jan 2, 2015

👍

arthurnn added a commit that referenced this pull request Jan 2, 2015
@arthurnn
Copy link
Contributor

arthurnn commented Jan 2, 2015

@durran
Copy link
Member Author

durran commented Jan 4, 2015

Thanks!

@matsimitsu
Copy link

I've tried to run Moped with this fix in production, but instead of a Moped::Errors::ConnectionFailure (Could not connect to a primary node for replica set ) I now get:

One: Moped::Errors::ConnectionFailure
and [pool size]: ConnectionPool::PoolShuttingDownError errors.

It happens at random throughout the app and only on one of our servers at the same time.

jonhyman pushed a commit to jonhyman/moped that referenced this pull request Apr 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Shouldn't node down! do a pool shutdown?
3 participants