mongodb connection timeout when mongodb is not in the same VM

Question

I have my MongoDB running on a Cloud VM , and NodeJS Server running on another Azure Cloud VM. I use Mongoose in the Application for MongoDB Connect. Keep getting this timeout issue every day? Any suggestions

events.js:72
        throw er; // Unhandled 'error' event
              ^
    Error: failed to connect to [XXXXX.cloudapp.net:27017]
        at null.<anonymous> (/app/satwebnodev2/satwebnodev2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:546:74)
        at emit (events.js:106:17)
        at null.<anonymous> (/app/satwebnodev2/satwebnodev2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:150:15)
        at emit (events.js:98:17)
        at Socket.<anonymous> (/app/satwebnodev2/satwebnodev2/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/connection.js:533:10)
        at Socket.emit (events.js:95:17)
        at net.js:440:14
        at process._tickCallback (node.js:419:13)

can you show some code, particularly the code where mongoose is connecting to the database — Mattias Farnemyhr
– Mattias Farnemyhr, Commented Sep 15, 2014 at 12:25
var mongoose = require('mongoose'); var options = { server: { socketOptions: { keepAlive: 20, connectTimeoutMS: 30000 } }}; mongoose.createConnection('db.url',options); — dddd2011
– dddd2011, Commented Sep 16, 2014 at 23:09

Ameya K · Accepted Answer · 2014-10-14 11:22:41Z

2

Refer this link :- http://www.slideshare.net/VictoriaMalaya1/mongo-db-in-windows-azure

MongoDB in Windows Azure:- Drawbacks and workarounds : connection timeout for .Net driver MongoDB Client Uses .Net driver socket timeout exception Windows Azure terminates an inactive connection after roughly 4 minutes of idling MongoDB suggests: Set the max idle connection time on the driver: MongoDefaults.MaxConnectionIdleTime = TimeSpan.FromMinutes(1); My experience: Add following options to connection string: maxIdleTimeMS=60000;connectTimeoutMS=60000;socketTimeoutMS=60000 Sample of connection string: connectionString="mongodb://localhost/mydb ?maxIdleTimeMS=60000;connectTimeoutMS=60000;socketTimeoutMS=60000"

answered Oct 14, 2014 at 11:22

Ameya K

211 bronze badge

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

mongodb connection timeout when mongodb is not in the same VM

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related