-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.43
-
Component/s: None
-
Labels:
-
Environment:Node.js v0.12.7
-
Empty show more show less
We run a 3 node replica set (all mongod v3.0.3) in 3 different AWS availability zones. 99% of the time we connect perfectly and have no problems. However with a certain script every once in a while (few times a day) we get back the error "no primary server available". Driver version is v2.0.42 as pulled in by npm.
Connection string follows this format:
mongodb://user:pass@10.0.0.1:27017,10.0.0.2:27017,10.0.0.3:27017/ourDb?authSource=admin&replicaSet=RS-0&ssl=true
We also pass the following object into the server settings:
serverOpts = {
server:
,
replSet:
};
Where "ca" is a loaded cert file for the SSL connection.
As mentioned this works everywhere bar this one script, and in this script the issue only shows a few times a day with the script running every 3 minutes do checks against out data.
Please note that v2.0.43 is selected in the affected version as v2.0.42 does not seem to exist, even though the package.json in the node_modules folder points to v2.0.42.