Repository navigation
mongodb: 3.3.2 driver unable to connect with replica set when one node is down. #6261
Description
MongoDB driver 3.3.2 is unable to connect to mongodb replicaSet if one of member machine is down.
Note: Same issue is described in https://jira.mongodb.org/browse/NODE-2231
Steps to reproduce
- Create mongodb replicaSet with 3 member.
- connect parse-server with mongodb providing all 3 member host name in uri.
- stop PRIMARY mongodb server
- MongoDB is able to select new PRIMARY from the available 2 member but parser-server is unable to connect to new PRIMARY mongodb node.
Note: Even we restart parse-server when one of the 3 member replicaSet mongodb is down and in mongo connection URI we have provided hostname for all the 3 member. It is not able to connect mongodb.
Expected Results
When one mongoDB replicaSet member goes down. It should automatically connect to new primary mongodb server.
Actual Outcome
Error: connect ECONNREFUSED x.x.x.x:port
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14) {
name: 'MongoNetworkError',
errorLabels: [ 'TransientTransactionError' ],
[Symbol(mongoErrorContextSymbol)]: {}
}
Environment Setup
-
Server
- parse-server : 3.9.0
- Operating System: Ubuntu 18.04
- Hardware: R4.2x.large
- Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): AWS
-
Database
- MongoDB version: 4.2 (also tested on 4.0.9)
- Storage engine: WireTigger
- Hardware: R4.2x.large
- Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): AWS
Activity
manjeshpv commentedon Dec 5, 2019
I'm also facing same issue
davimacedo commentedon Dec 5, 2019
As per the link you sent, it looks that updating the MongoDB package to the latest version should fix the problem. @dplewis why did you close #6242? Didn't it pass the tests?
dplewis commentedon Dec 5, 2019
#6135 (comment)
The test have been failing, it should be an easy fix. I can look into it again shortly
davimacedo commentedon Dec 5, 2019
Sorry. I missed that one. Let me know if you need any help.
dplewis commentedon Dec 5, 2019
@yog27ray Can you try to see if the latest mongo driver update fixed your issue?
I should have a replica set somewhere to test with.
@davimacedo I’ll need help since I’ve been closing them. I haven’t had luck so far. At least we know where the issue is coming from.
yog27ray commentedon Dec 5, 2019
@dplewis latest mongo driver has fixed my issue.
Below are the steps I used to confirm that latest mongo driver is fixing the issue.
now even if I stop any replica member, parse-server is able to switch connection to other replica member and even i restart parse-server while keeping one member down it is able to communicate with other replica member.
We already configured replica set to verify the same if you want we can share the same with you.
dplewis commentedon Dec 6, 2019
I opened a PR #6263 for this. All the tests passes locally. Hopefully someone can fix the travis issues. Its up for grabs.