From user-return-20128-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Mar 20 14:20:41 2012 Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2756997EE for ; Tue, 20 Mar 2012 14:20:41 +0000 (UTC) Received: (qmail 52402 invoked by uid 500); 20 Mar 2012 14:20:39 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 52369 invoked by uid 500); 20 Mar 2012 14:20:39 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 52361 invoked by uid 99); 20 Mar 2012 14:20:39 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2012 14:20:39 +0000 Received: from localhost (HELO mail-ey0-f180.google.com) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2012 14:20:39 +0000 Received: by eaal12 with SMTP id l12so32975eaa.11 for ; Tue, 20 Mar 2012 07:20:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.181.164 with SMTP id dx4mr5442161igc.1.1332253236458; Tue, 20 Mar 2012 07:20:36 -0700 (PDT) Received: by 10.42.99.195 with HTTP; Tue, 20 Mar 2012 07:20:36 -0700 (PDT) In-Reply-To: References: <0D590A87-0540-4143-9F60-F95D18D458F3@thenoi.se> <4F6880F5.70309@gmail.com> <1BC133D6-7324-4A5A-B281-0F9C089B8E6D@thenoi.se> Date: Tue, 20 Mar 2012 14:20:36 +0000 Message-ID: Subject: Re: CouchDB, linux & clean shutdowns From: Robert Newson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 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. 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. B. On 20 March 2012 13:51, Jason Smith wrote: > On Tue, Mar 20, 2012 at 1:38 PM, Martin Hewitt wrote: >> Hi Alexander, >> >> On 20 Mar 2012, at 13:23, Alexander Shorin wrote: >> >>> On Tue, Mar 20, 2012 at 5:07 PM, Jo-Erlend Schinstad >>> wrote: >>>> As far as I'm aware, there's no clean way to shutdown CouchDB. It's designed >>>> that way. You just kill it. >>> >>> With _admin permissions: >>> curl -X POST http://localhost:5984/_restart -H "Content-Type: application/json" >> >> Excellent, thanks, I'll give this a try. >> >>> >>> On Tue, Mar 20, 2012 at 5:12 PM, Martin Hewitt wrote: >>>>> What version are you running? >>>> >>>> Running 1.2.0a-1160734, compiled from source some time back. >>> >>> 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? >> >> 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. > > Hi, Martin. I wonder if it is related to this issue? > > 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.) > > > -- > Iris Couch