couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <>
Subject [jira] Commented: (COUCHDB-1052) CouchDB crashes by Erlang Heartbeat Runtime System
Date Tue, 22 Feb 2011 22:02:38 GMT


Randall Leeds commented on COUCHDB-1052:

bin/couchdb includes the option "-r" for passing a respawn timeout on the command line.

The init script uses an environment variable called COUCHDB_RESPAWN_TIMEOUT which is passed
to /usr/bin/couchdb with this option.
If you use the init script, you'll notice that it will source a file (in your case, given
your installation path, maybe /opt/couchdb/etc/default/couchdb) to get the environment.
COUCHDB_RESPAWN_TIMEOUT is set in there if you'd like to use the init script.

Otherwise, calling couchdb with "-r 1" should do what you want.

> CouchDB crashes by Erlang Heartbeat Runtime System
> --------------------------------------------------
>                 Key: COUCHDB-1052
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: 0.10.1, 1.0.1
>         Environment: Solaris 10
>            Reporter: Nicolas Maupu
>         Attachments: couchdb-bin-1.0.1.diff
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> Hello,
> We have several couchdb in our production environment (starting from 0.10.1 and upgraded
to 1.0.1). Some instances began to crash several times a day.
> After research (I am not aware of all erlang tips and tricks), I found that the problem
was caused by erlang heartbeat runtime system (
> For some reasons (it seems to be a problem with system clock), this heartbeat process
sends a signal to main erlang process to trigger HEARTBEAT_COMMAND. 
> The command configured by couchdb startup script is to call 'bin/couchdb -k' which kill
server ...
> I don't know if this is wanted or not but is Erlang heartbeat system provided to restart
a service if this one crash ?
> I patched mine to restart process gracefully but I would like to know if this is a feature
or a bug : next time I upgrade, I will have to patch again.
> My patch is a little bit specific to my architecture so I did not provide it. Ask me
if you are interested.
> nm.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message