incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luca Morandini <lmorand...@ieee.org>
Subject Unclosed connections to CouchDB using Cradle
Date Mon, 25 Feb 2013 23:51:30 GMT
Folks,

I have set up an application using Cradle 0.6.4 connected to CouchDB 1.2.0, and 
started stress testing it... and encountered an issue.

After setting up a simulated load -using nodeload- of 60 users each requesting 100 
documents of about 60MB (they vary from a few bytes to 60MB, but most of them are 
60MB) I found out that some connections to CouchDB were not closed after the load 
program terminated.

I have set the maxSockets parameters of both http module and Cradle to 50, hence 
the app ramps up to 110 open connections, then the number of connections 
decreases... but some of them remains in an "ESTABLISHED" status.

Here's the netstat output:
tcp   5896064 0 127.0.0.1:37968 127.0.0.1:5984 ESTABLISHED 31914/node
tcp   6051609 0 127.0.0.1:37977 127.0.0.1:5984 ESTABLISHED 31914/node
tcp   1095733 0 127.0.0.1:37947 127.0.0.1:5984 ESTABLISHED 31914/node
tcp   1590408 0 127.0.0.1:37949 127.0.0.1:5984 ESTABLISHED 31914/node

All of them are connections from my app to CouchDB: is there any way to prevent 
this or -failing that- force a periodic closing ?

Regards,

Luca Morandini
Data Architect - AURIN project
Department of Computing and Information Systems
University of Melbourne
Tel. +61 03 903 58 380
Skype: lmorandini


Mime
View raw message