Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.132.245 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=D0Zo3WlxCrXW+4snxrRZqkNcaBbh5Gh53Daigmsk3J5vMFnt0/bFI3StHr5PVZ622/
         8L2zL2YYt+fRX7JNdUJAR9/EOjCZ2daSh/4VsiAw/4aOtmrN8Yfk4HVIoIT0SjPReruj
         rrW2GO6xiOErmRLSTF1Jvldws4cGawLQNEHNo=
MIME-Version: 1.0
In-Reply-To: <e2e56d2e0909062039w29d34a57jf7e0b26d10a4ab6e@mail.gmail.com>
References: <e2e56d2e0909062018s1bc09373yac75a8b7cf6b5aa1@mail.gmail.com>
	 <e2111bbb0909062024t4066a0bbybe8e31f73300f57b@mail.gmail.com>
	 <e2e56d2e0909062039w29d34a57jf7e0b26d10a4ab6e@mail.gmail.com>
Date: Mon, 7 Sep 2009 00:18:46 -0400
Message-ID: <e2111bbb0909062118if6d4a03h349bf226d67ea099@mail.gmail.com>
Subject: Re: Multiple couchjs processes being spawned
From: Paul Davis <paul.joseph.davis@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Another random thought, after your clients have been running a bit, an
easy way to check why type of stuff is going on with sockets is:

$ netstat -ap tcp

If your apps have periods of high turnover, check the sockets to see
if you have lots of them in TIME_WAIT state.

Paul

On Sun, Sep 6, 2009 at 11:39 PM, Arun Thampi<arun.thampi@gmail.com> wrote:
> 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 <paul.joseph.davis@gmail.com>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<arun.thampi@gmail.com> 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
>