未加星标

Connection Pool for NodeJS

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二04 | 时间 2018 | 作者 红领巾 ] 0人收藏点击收藏

I have an app that has been maxing out the number of connection to MongoDB and I was under the assumption that if the drivers were set up correctly you didn't need to worry about closing connections.

I've seen people mention the Generic Pool module but what is the best process for closing or pooling connections using Node & MongoDB?

Here is my connection code for the app:

var sys = require("sys"); var app = require('http').createServer(handler); var io = require('socket.io').listen(app); app.listen(1337); io.configure(function () { io.set('authorization', function (handshakeData, callback) { callback(null, true); }); }); function handler (req, res, data) { sys.puts('request made to trackerapp.js'); res.writeHead(200); res.end(data); } io.sockets.on('connection', function (socket) { socket.on('adTracker', function (data) { var adRequestData = data; var databaseUrl = "mongodb://dbuser:dbpass@mongolab.com/tracker"; var collections = ["cmnads"] var db = require("mongojs").connect(databaseUrl, collections); db.cmnads.insert({adRequest : adRequestData},function(err, updated) { if( err || !updated ) console.log("mongo not updated" + err); else console.log("data stored"); }); }); });

Problem courtesy of: HjalmarCarlson

Solution

After seeing JohnnyHK's comment I was able to pull the connection event out of the Socket.io connection and it worked fine, see the solution below:

var databaseUrl = "mongodb://dbuser:dbpass@mongolab.com/tracker"; var collections = ["cmnads"]; var db = mongojs.connect(databaseUrl, collections); io.sockets.on('connection', function (socket) { socket.on('adTracker', function (data) { var adRequestData = data; //vars for MongoDB used to be created here... so new connect function was called on every request to socket.io db.cmnads.insert({adRequest : adRequestData},function(err, updated) { if( err || !updated ) console.log("mongo not updated" + err); else console.log("data stored"); }); }); });

Solution courtesy of: HjalmarCarlson

Discussion

A technique I used with my express apps that seems have some measure of success is to open a connection to a mongo instance (thereby getting a connection pool) then sharing that db (that is now in the "connected" state) instance wherever it is needed. Something like this:

server = new Server(app.settings.dbsettings.host, app.settings.dbsettings.port, {auto_reconnect: true, poolSize: 5}) db = new Db(app.settings.dbsettings.db, server, {native_parser:false}) db.open(function(err, db) { app.db = db; server = app.listen(app.settings.port); console.log("Express server listening on port %d in %s mode", app.settings.port, app.settings.env); require('./apps/socket-io')(app, server); });

This connects to the database at the highest level in my app before the program moves into the wait listen state.

Before I used this pattern I would create a new database object whenever I needed to interact with the database. The problem I found is that the new database object would create a new thread pool, consuming a bunch of ports. These were never cleaned up properly. After a period of time the machine that hosted the app would run out of ports!

Anyway, a variation on the code I have shown should be where you should do your thinking I believe.

Discussion courtesy of: JB.

This recipe can be found in it's original form on Stack Over Flow .

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

分页:12
转载请注明
本文标题:Connection Pool for NodeJS
本站链接:https://www.codesec.net/view/611858.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(9)