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: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: CouchDB, linux & clean shutdowns
From: Martin Hewitt <martin@thenoi.se>
In-Reply-To: 
 <CABvT1DFUpAL385saFUxQSY=S-6o-kySfcn=hs7XQ=7Z8f3nfJg@mail.gmail.com>
Date: Tue, 20 Mar 2012 16:33:09 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A997CC7-B3D6-4FEF-9482-957F69AE7F12@thenoi.se>
References: <0D590A87-0540-4143-9F60-F95D18D458F3@thenoi.se>
 <4F6880F5.70309@gmail.com>
 <CAHdjipJU8tJPBmWTGyQ3foRmYbNGLzcYa5nowz1ajg+a004bLQ@mail.gmail.com>
 <1BC133D6-7324-4A5A-B281-0F9C089B8E6D@thenoi.se>
 <CAN-3CBKN9YPr1qOk6H6Q=z57eTwHojcH6QbUx8BvXcngyLzbHA@mail.gmail.com>
 <CABvT1DE7_h6JniMJWxiaVqXCk6RvAQafm4RrzDTANe8UdKOK1w@mail.gmail.com>
 <CABvT1DFUpAL385saFUxQSY=S-6o-kySfcn=hs7XQ=7Z8f3nfJg@mail.gmail.com>
To: user@couchdb.apache.org

Hi Robert,

For one view, whenever we loaded it, but every time we loaded it, would =
produce a stack trace and not the view. Restarting the CouchDB instance =
restored the view to working order.

I'll try and dig out the stack trace, but it was the perpetual, =
continual problem with this view that led us to take the "nuclear =
option" and restart.

Martin

On 20 Mar 2012, at 14:24, Robert Newson wrote:

> Can you describe "it was repeatedly crashing with gen_server timeouts"
> in more detail? This sounds non-fatal to me but can look alarming if
> you're not used to the erlang approach to error handling. It might be
> that you're restarting for no good reason.
>=20
> B.
>=20
> On 20 March 2012 14:20, Robert Newson <rnewson@apache.org> wrote:
>> Also we don't fsync views at all, so if you built the view and then
>> killed couchdb very quickly, the data didn't reach the platters.
>>=20
>> I'll note that you really, *really*, want to set delayed_commits to
>> false if using couchdb in production. This strongly guarantees that
>> your database updates are preserved in the event of a crash.
>>=20
>> B.
>>=20
>> On 20 March 2012 13:51, Jason Smith <jhs@iriscouch.com> wrote:
>>> On Tue, Mar 20, 2012 at 1:38 PM, Martin Hewitt <martin@thenoi.se> =
wrote:
>>>> Hi Alexander,
>>>>=20
>>>> On 20 Mar 2012, at 13:23, Alexander Shorin wrote:
>>>>=20
>>>>> On Tue, Mar 20, 2012 at 5:07 PM, Jo-Erlend Schinstad
>>>>> <joerlend.schinstad@gmail.com> wrote:
>>>>>> As far as I'm aware, there's no clean way to shutdown CouchDB. =
It's designed
>>>>>> that way. You just kill it.
>>>>>=20
>>>>> With _admin permissions:
>>>>> curl -X POST http://localhost:5984/_restart -H "Content-Type: =
application/json"
>>>>=20
>>>> Excellent, thanks, I'll give this a try.
>>>>=20
>>>>>=20
>>>>> On Tue, Mar 20, 2012 at 5:12 PM, Martin Hewitt <martin@thenoi.se> =
wrote:
>>>>>>> What version are you running?
>>>>>>=20
>>>>>> Running 1.2.0a-1160734, compiled from source some time back.
>>>>>=20
>>>>> Looks like subversion revision number and a little out of dated. =
By
>>>>> the way, CouchDB repository had been moved to git not so far a =
long
>>>>> ago. Have you tried to update to latest head of 1.2.x branch?
>>>>=20
>>>> Yeah, i know it's an old version, I was just curious as to whether =
there was something I could try before rebuilding the server.
>>>=20
>>> Hi, Martin. I wonder if it is related to this issue?
>>>=20
>>> CouchDB was deleting .view files if some kinds of errors happened.
>>> This will be fixed in the upcoming version 1.2.0. (But I'm not 100%
>>> sure that that is your issue.)
>>>=20
>>>=20
>>> --
>>> Iris Couch