couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Smith <...@iriscouch.com>
Subject Re: [jira] [Commented] (COUCHDB-1357) Authentication failure after updating password in user document
Date Fri, 09 Dec 2011 02:06:09 GMT
Hi, Pete. I didn't want to derail the JIRA thread.

On Fri, Dec 9, 2011 at 12:23 AM, Pete Vander Giessen (Commented)
(JIRA) <jira@apache.org> wrote:
> One more question: is there are generic way to tell when a view server has crashed, and
we may need to restart couchdb? It sounds like I can make the problem I ran into less likely
to occur by increasing file/process limits, but I'd like to add some sort of watchdog process
that will let me know that I've hit a limit, and that my _users view server, for example,
may be crashed ...

I am unsure if there is a catch-all technique to detect availability
issues. But the recent Google Plus essay by Steve Yegge makes a good
point that the best technique is to actually exercise the service and
decide for yourself whether it is up or down.

That is the idea behind a plugin I wrote, pingquery_couchdb:
https://github.com/iriscouch/pingquery_couchdb

At Iris Couch, we saw accounts going down occasionally where the
Erlang components (HTTP server and database operations) worked, but
views had stopped building, _show and _list functions timed out, etc.
The pingquery plugin allows probing more deeply into a Couch app's
guts.

Probe CouchDB will detect this plugin and ping the javascript and
coffeescript query servers, throwing an error if they fail.

https://github.com/iriscouch/probe_couchdb

-- 
Iris Couch

Mime
View raw message