Thanks Paul for the quick response. I'll poke around further to see if there is anything amiss and will keep the list posted. Cheers, Arun
On Mon, Sep 7, 2009 at 11:24 AM, Paul Davis <[email protected]>wrote: > The algorithm for CouchDB's use of OS processes is pretty simple: > > "Give me an os process plz" > > If none are available, then it creates a new one. A large number of OS > processes would suggest to me that something isn't releasing OS > processes correctly. My first guess would be to look at _list and > _show as those both require an OS process, but are also at the mercy > of client connection semantics. I might be reaching a bit, but I > wonder if CouchRest is failing to close sockets properly. Its not much > more than a random finger pointing, but there have been other errors > recently that also suggest CouchRest isn't doing proper socket > handling. > > The other possibility is there's something weird with killing > processes, but couchspawnkillable should've fixed that. > > HTH, > Paul Davis > > On Sun, Sep 6, 2009 at 11:18 PM, Arun Thampi<[email protected]> wrote: > > Hi guys - Been running CouchDB trunk(r804727) in production for about 3 > > weeks now and one thing I've noticed is that the number of couchjs > processes > > (/usr/local/lib/couchdb/bin/couchjs > /usr/local/share/couchdb/server/main.js) > > keeps increasing to a large amount. Is this normal? Does CouchDB manage > > these processes and eventually kill inactive couchjs processes? > > Just FYI I'm using CouchRest as part of a Rails app to query two > different > > views in my db. > > > > Thanks in advance. > > > > Cheers, > > Arun > > > > -- > > It's better to be a pirate than join the Navy - Steve Jobs > > http://mclov.in > > > -- It's better to be a pirate than join the Navy - Steve Jobs http://mclov.in
