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 seggy.umboh@gmail.com
 designates 209.85.210.203 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=OLEQeL8C3klSVx2GyRfANp2nGRUwKGidA8v3sqJpVByYuzDC4VydlhRdWFBNgdQj3A
         VJ4MUFWyVSd4aGU87yndtFNCHGNh0zffKPmdCBsehR0VJX/Sq3WI4290ecoKR3WSMFji
         zxb5NZCP23era9BRPRjymB5TbxAmgcurMp07E=
MIME-Version: 1.0
In-Reply-To: <e2111bbb0910061313l46f0272fg6e84a1de84397e9e@mail.gmail.com>
References: <6cfccb3d0910030910m678c9157o811a57e02ffbeff0@mail.gmail.com>
	 <6cfccb3d0910031824q5d9362c2k7719b32a779e956f@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>
	 <e2111bbb0910061313l46f0272fg6e84a1de84397e9e@mail.gmail.com>
Date: Tue, 6 Oct 2009 13:26:56 -0700
Message-ID: <a153de6d0910061326l704a3b1cr19016a4b4cea8d59@mail.gmail.com>
Subject: Re: Timeout Error when trying to access views + Indexing problems
From: Seggy Umboh <seggy.umboh@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016368324b233bab204754a0d07

--0016368324b233bab204754a0d07
Content-Type: text/plain; charset=UTF-8

Glenn,
Since you are running on EC2, may I also suggest you put the couchdb data
directory on a EBS volume and snapshot it if you have not already, that way
you can spin up EC2 instances to try each of the suggestions being given on
the list on separate copies of the data

Good luck!


On Tue, Oct 6, 2009 at 1:13 PM, Paul Davis <paul.joseph.davis@gmail.com>wrote:

> On Tue, Oct 6, 2009 at 3:42 PM, Glenn Rempe <glenn@rempe.us> 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 <kocolosk@apache.org>
> 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.
>

--0016368324b233bab204754a0d07--