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 ryan@kumu.io designates
 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJNb-9oaOfjeR5P4O4o-ycEmp_-NeTW1AdZs-4=H=T9cEiZYcg@mail.gmail.com>
References: 
 <CAOA1H+LfhySkCNk1F0B-Bh4Y0vhjCMiSVr2ChwJt1Fm0vd5-qA@mail.gmail.com>
 <CAJNb-9oaOfjeR5P4O4o-ycEmp_-NeTW1AdZs-4=H=T9cEiZYcg@mail.gmail.com>
From: Ryan Mohr <ryan@kumu.io>
Date: Fri, 11 Jul 2014 08:47:57 -1000
Message-ID: 
 <CAOA1H++EvScRRfvto45y8GaXnV5gzQ5axbY9ZmN=B08C=g19rw@mail.gmail.com>
Subject: Re: Are couchdb restarts graceful?
To: user <user@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=f46d04374a05a6a7ad04fdef6368

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

In the end the errors ended up (ironically) being caused by a bad call to
our error monitoring service.  We run couchdb behind a rails proxy and we
were randomly seeing 500 errors on some proxy requests with no backtrace so
it was hard to track down.

Benoit, by graceful I mean something like unicorn's USR2 signal.  The
original process would immediately stop accepting new requests, fire up a
new instance, finish handling any existing requests, and then terminate.

Is there a strong argument against graceful restarts?  Couchdb restarts so
quickly it's a shame to have it result in failed requests.

--f46d04374a05a6a7ad04fdef6368--