[erlang-bugs] heart prevents beam from creating crash dumps

Jonas Boberg <>
Mon Aug 27 12:36:51 CEST 2012


> I would not be surprised that preparing a dump and writing it to disk can typically take more than 30 seconds.

Definitely. On systems with lots of RAM (48 GB in this case), writing
the crash dump takes several minutes.

Ideally the heart behavior should be configurable. Normally we don't
want to wait several minutes for heart to kill the node, so that it
comes back up. Sometimes when investigating a production crash though,
we would like to configure heart to wait for the crash dump to be
written.


More information about the erlang-bugs mailing list