Databases
StackOverflow2013
Postsdbo
PODoes mongoDB have reconnect issues or am i doing it wrong?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODoes mongoDB have reconnect issues or am i doing it wrong?
    primarykey
    data
    text
    <p>I'm using nodejs and a mongoDB - and I'm having some connection issues.</p> <p>Well, actually "wake" issues! It connects perfectly well - is super fast and I'm generally happy with the results.</p> <p><strong>My problem:</strong> If i don't use the connection for a while (i say while, because the timeframe varies 5+ mins) it seems to stall. I don't get disconnection events fired - it just hangs. </p> <p>Eventually i get a response like Error: failed to connect to [ * .mongolab.com: * ] - ( * = masked values)</p> <p>A quick restart of the app, and the connection's great again. Sometimes, if i don't restart the app, i can refresh and it reconnects happily.</p> <p>This is why i think it is "wake" issues.</p> <p><strong>Rough outline of code:</strong></p> <p>I've not included the code - I don't think it's needed. It works (apart from the connection dropout)</p> <p><strong>Things to note:</strong> There is just the one "connect" - i never close it. I never reopen.</p> <p>I'm using mongoose, socketio.</p> <pre><code>/* constants */ var mongoConnect = 'myworkingconnectionstring-includingDBname'; /* includes */ /* settings */ /* Schema */ var db = mongoose.connect(mongoConnect); /* Socketio */ io.configure(function (){ io.set('authorization', function (handshakeData, callback) { }); }); io.sockets.on('connection', function (socket) { });//sockets io.sockets.on('disconnect', function(socket) { console.log('socket disconnection') }); /* The Routing */ app.post('/login', function(req, res){ }); app.get('/invited', function(req, res){ }); app.get('/', function(req, res){ }); app.get('/logout', function(req, res){ }); app.get('/error', function(req, res){ }); server.listen(port); console.log('Listening on port '+port); db.connection.on('error', function(err) { console.log("DB connection Error: "+err); }); db.connection.on('open', function() { console.log("DB connected"); }); db.connection.on('close', function(str) { console.log("DB disconnected: "+str); }); </code></pre> <p>I have tried various configs here, like opening and closing all the time - I believe though, the general consensus is to do as i am with one open wrapping the lot. ??</p> <p>I have tried a connection tester, that keeps checking the status of the connection... even though this appears to say everthing's ok - the issue still happens.</p> <p>I have had this issue from day one. I have always hosted the MongoDB with MongoLab. The problem appears to be worse on localhost. But i still have the issue on Azure and now nodejit.su.</p> <p>As it happens everywhere - it must be me, MongoDB, or mongolab.</p> <p>Incidentally i have had a similar experience with the php driver too. (to confirm this is on nodejs though)</p> <p>It would be great for some help - even if someone just says "this is normal"</p> <p>thanks in advance</p> <p>Rob</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjared
    1. USrob_james
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODoes mongoDB have reconnect issues or am i doing it wrong?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODoes mongoDB have reconnect issues or am i doing it wrong?
      1. USzee
      1. VTFavorite
    3. VO
      singulars
      1. PODoes mongoDB have reconnect issues or am i doing it wrong?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CONot sure about MongoDB, but in most (traditional databases) it's better to open/close the connection on demand (i.e. everytime you need to access it) rather than leaving it open forever. Database drivers are usually optimized to create and manage a pool connections behind the scenes so this (opening/closing) tends to be incredibly fast. I would be curious to hear what people with real MongoDB experience say on this question too.
      singulars
      1. PODoes mongoDB have reconnect issues or am i doing it wrong?
      1. USHector Correa
    2. COThanks Hector - yeah agreed, only everywhere i read when investigating this says to do it the way i have (unless i understand incorrectly)
      singulars
      1. PODoes mongoDB have reconnect issues or am i doing it wrong?
      1. USrob_james
    3. COI get the same problem against both MongoHQ and MongoLab instances--not only from my Node app, but from the mongo command-line client too. MongoHQ support suggested I handle this at a app or driver level by retrying when this happens. It's such a pain to handle this at an app level that I'm surprised this isn't already handled in the mongodb driver or in mongoose.
      singulars
      1. PODoes mongoDB have reconnect issues or am i doing it wrong?
      1. USMike M. Lin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload