-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DB reconnect when connection lost occurred #57
Comments
Pinging the database is in my opinion the best solution, I have to export it so people don't need to go deep in the ORM object to do it. Dropping the connection and reconnecting takes time and resources (client goes offline, free mem, client comes online again, alloc mem, ..). I think pinging and having the connection idle improves startup time (on requests) and has almost no impact in the database (assuming you have only 1 connection per app and not 1 per request). |
Thank you for your reply. I have understood your point, so I'll continue to use db.ping(). |
Is it possible to catch and handle 'connection lost' event and try to reconnect to db now?
I use mysql driver and I have wait_timeout set in mysql config, so, if connection is inactive for some time, mysql closes it and node-mysql throws an error.
I tryed to catch it with
db.driver.on
ordb.driver.db.on
, but no success.So, I have two questions:
db.driver.db.on
? As far as I understand, db.driver.on is an instance of node-mysql connection. But, when I do:everything works well, and, when I do:
node-mysql just throws unhandled exception and the whole process ends.
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: