On Mon, Jul 12, 2010 at 23:47, J Chris Anderson <[email protected]> wrote: > This is usually a symptom that Erlang is unable to allocate memory. When that > happens, it just goes away, no logs, no nothing. > > It could be the disk wait is cause mochiweb to continue to accept sockets, > and allocate processes to handle the connections, until at some point there > is no memory left to allocate. > > One option is to configure the max_connections # to be smaller. > > But I am just stabbing in the dark here as to the cause of the memory > over-usage. > > And yes it could be the OS killing Couch for other reasons. > > There is a heartbeat option which ought to be the robust fix for this (it > will reboot couch automatically). Someone else on this list will know better > than I, how to ensure that it runs.
We've also been seeing this with one of our CouchDB servers at work. It seems to die when a (rsync) backup process gets kicked off by cron. I've verified that it's not the Linux OOM killer killing CouchDB, so I would like to hear more about the heartbeat option thing. Cheers, Dirkjan
