My CouchDB (production) server sometimes shuts down, without my desire. When checking the logs, I noticed that Erlang / CouchDB (one or the other) sends a heart rate, and this heart rate is controlled. When a timeout occurs, the server is brutally killed ( couchdb -k). This is almost always an undesirable behavior, specifically on a production server.
I ran into this problem , which states the same thing and indicates that this happens mainly during heavy server loads, which I also noticed.
I am looking for a solution to keep my server running, but for this I need to learn more about this behavior. Unfortunately, the wiki wiki and manual do not provide much information about this (only a parameter in the change API).
Can anyone provide more information about this?
source
share