Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <4D517B48.4060004@gpslsolutions.com>
References: <4D517B48.4060004@gpslsolutions.com>
Date: Wed, 9 Feb 2011 22:45:40 +1300
Message-ID: <AANLkTi=78RXC4Q2WdkFUGh_VC6w3DAOiLEcoNsyz7vay@mail.gmail.com>
Subject: Re: Views crash
From: Dave Cottlehuber <dave@muse.net.nz>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 9 February 2011 06:20, Rob Pettefar <rpettefar@gpslsolutions.com> wrote:
> =A0Hi guys
> I have an issue with views crashing.
> This has occurred on both Linux and Windows distributions of CouchDB 1.0.=
1

Has this issue occurred on those platforms, on a previous version?

> Sometimes the views for a particular database will break. In Futon they
> appear unresponsive.
> The only way round this that I have seen is to delete and rebuild the vie=
w
> file for the database in question.
>
> This seems to happen more often on the Windows version but I don't think =
it
> is anything to do with the >4Gb file issue.
> Any help you could lend would be invaluable.
>
> Thanks
> Rob
>
> I have included the error that was logged in the couchdb log file:
>
> [Fri, 21 Jan 2011 12:18:28 GMT] [debug] [<0.738.0>] Exit from linked pid:
> {<0.742.0>,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {timeout,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {gen_server,call,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [couch_query_=
servers,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{get_proc,=
<<"javascript">>}]}}}
>
> [Fri, 21 Jan 2011 12:18:28 GMT] [error] [<0.738.0>] ** Generic server
> <0.738.0> terminating
> ** Last message in was {'EXIT',<0.742.0>,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {timeout,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {gen_server,c=
all,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [couc=
h_query_servers,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{g=
et_proc,<<"javascript">>}]}}}
> ** When Server state =3D=3D {group_state,undefined,<<"testdb">>,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 {"../var/lib/couchdb",<<"=
testdb">>,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{group,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [<<"npc">>],

Hi Rob

by no means am I am expert but it looks like this is a "normal"
timeout in couch_query_servers.

    ProcTimeout =3D list_to_integer(couch_config:get(
                        "couchdb", "os_process_timeout", "5000")),

If so you can try upping this from the default 5 seconds in local.ini:

[couchdb]
os_process_timeout =3D 5000 ; 5 seconds. for view and external servers.

& restart.

The more important question is - why should these views take so long to pro=
cess?

A+
Dave