couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <>
Subject Re: Timeout Error when trying to access views + Indexing problems
Date Tue, 06 Oct 2009 20:13:29 GMT
On Tue, Oct 6, 2009 at 3:42 PM, Glenn Rempe <> wrote:
> Is there some way we can instrument and log how much memory the VM
> thinks it has somewhere in the critical path piece of erlang code?  Or
> is there another way I can track that externally?
> G
> On Tue, Oct 6, 2009 at 12:13 PM, Adam Kocoloski <> wrote:
>> On Oct 6, 2009, at 2:46 AM, Glenn Rempe wrote:
>> TMI logging doesn't really exist, no one uses that level internally.  I
>> agree with Paul here, the lack of error messages indicates an instant VM
>> death.  The most common way to cause that is by running out of memory, but
>> view indexing is not supposed to use a large amount of memory at all.
>> Adam

Here's a quick and dirty script that should work ish I think probably.
I only tested it minimally. As it, no syntax errors and it prints the
first vm size as expected.

Just run that in a terminal while the indexer runs. It should die at
the same time the the Erlang process dies.

View raw message