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 dionne@dionne-associates.com
 designates 69.89.22.10 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default;
 d=dionne-associates.com;
	h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Identified-User;
	b=mMTZLHwHVQO3daQu+Q+vbXnU4w32bSNM/K9ZhnrpfGZgiaC2zs+we9rJCgtn8nB8aVnRdrgAEp8Xd2+/HSH3CjLIA1U2XAYrORhtGfMmMZR54+PliA4NEQAyeDwRTo5z;
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: Re: Timeout Error when trying to access views + Indexing problems
From: Robert Dionne <dionne@dionne-associates.com>
In-Reply-To: <6cfccb3d0910061451h459d6113qf8e15ce1d112c6d2@mail.gmail.com>
Date: Tue, 6 Oct 2009 18:45:32 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DAFF98CC-BD63-45A1-B388-1D8E3A56B966@dionne-associates.com>
References: <6cfccb3d0910030910m678c9157o811a57e02ffbeff0@mail.gmail.com>
  <1521F562-7878-423B-BEC3-FF2A1916DA0C@gmail.com>
 <6cfccb3d0910032307i1df64f79u437d5c803bff2c50@mail.gmail.com>
  <A60F21CC-9C57-4202-84C1-04BEF84CD141@apache.org>
 <6cfccb3d0910052346hb4ca0b3o7eb6e77fec4ac1a7@mail.gmail.com>
  <99817787-2B70-4346-A4BA-21C7C258AC65@apache.org>
 <6cfccb3d0910061242s33be1bb5j9dbffb8dd7091c25@mail.gmail.com>
  <538FD38A-DE89-4F53-8B2C-D6DF90B9774C@dionne-associates.com>
  <6cfccb3d0910061301u2e31ec5cr6558e62e4f580668@mail.gmail.com>
  <72DAF136-CF13-48B2-8DD0-31E5E7BE04D1@dionne-associates.com>
 <6cfccb3d0910061451h459d6113qf8e15ce1d112c6d2@mail.gmail.com>
To: user@couchdb.apache.org

erlang:processes() will give you the list of pids. The function self()  
just returns the current pid, so you can call erlang:process_info(pid,  
memory)  for any process. However you'd really need to know which pid  
is causing the problem. I just thought the +d might provide a  
crash.dmp that might help determine if in fact the VM is blowing memory.


On Oct 6, 2009, at 5:51 PM, Glenn Rempe wrote:

> Hi Bob,
>
> I have the CouchDB running in interactive mode and I added the +d to a
> copy of the couchdb startup script immediately after the 'erl' call.
>
> I was wondering, is it possible, from within the erl shell to find
> specific processes and manually issue the 'erlang:process_info (self
> (), memory)' call from within the shell?
>
> Of course that would presume I know which process to monitor.  Which I
> don't really (And doing a ctrl-C in the shell and choosing the (p)
> options gives me a *huge* dump of info.)
>
> G
>
> On Tue, Oct 6, 2009 at 2:05 PM, Robert Dionne
> <dionne@dionne-associates.com> wrote:
>> sorry I was jumping in and hadn't read this entire thread yet. In  
>> your
>> startup script look for the erlang command "erl ...." and add a +d
>>
>> or prefix your script invocation with ERL_FLAGS=+d .....
>>
>> I usually run out of trunk and would use a command like ERL_FLAGS=+d
>> ./utils/run -i      where the -i makes it interactive so one can  
>> execute
>> commands in an erlang shell. To use process_info you'd need to know  
>> where to
>> insert statements in the code and rebuild. So your best best for  
>> now is to
>> try the other suggestions first.
>>
>> If you're new to couchdb there's an IRC channel, #couchdb that  
>> usually has a
>> few devs in there who can provide quicker turnaround on ideas, good  
>> and bad
>> :)
>>
>> Cheers,
>>
>> Bob
>>
>>
>>
>>
>> On Oct 6, 2009, at 4:01 PM, Glenn Rempe wrote:
>>
>>> Thanks Robert.  No I have not tried the +d option and I don't see  
>>> that
>>> as one of the options on the 'couchdb' starter script.  (Frankly I
>>> don't know how to do that having only just begun to dabble in  
>>> Erlang.)
>>> Can you give me more information on how I would provide that option
>>> exactly?
>>>
>>> Regarding the instrumentation.  That sounds great.  But again, I am
>>> not familiar enough with the internals of the CouchDB code to know
>>> just where I should put that.  Is there someone that could help me
>>> with that and we can create a custom build of CouchDB that I can  
>>> run?
>>>
>>> Thanks for chiming into the conversation.  Much appreciated.
>>>
>>> Glenn
>>>
>>> On Tue, Oct 6, 2009 at 12:48 PM, Robert Dionne
>>> <dionne@dionne-associates.com> wrote:
>>>>
>>>> Internally you can put some erlang:process_info (self (), memory)
>>>> statements
>>>> in.
>>
>>
>
>
>
> -- 
> Glenn Rempe
>
> email                 : glenn@rempe.us
> voice                 : (415) 894-5366 or (415)-89G-LENN
> twitter                : @grempe
> contact info        : http://www.rempe.us/contact.html
> pgp                    : http://www.rempe.us/gnupg.txt