<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;">hello,<div id="yiv1665829919"><div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div><br></div><div>I have a problem with Erlang VM running out of memory and dying. With this I have a question about correct recovery mechanisms which involve multiple VMs. <br></div><div><br></div><div>what is the correct way to recover "stateful" Erlang application? In my case, the app. which is crashing is a complex hierarchy of fsm_processes each containing certain state. I understand how to recover stateless processes with supervisors but what is the correct way to recovery stateful apps? Clearly in my case I
probably need some kind of supervisor 'node' but what would be the steps to correctly recover killed processes with their states? do I need to use a db and replay the processes from disk on another node or can I have a node with identical processes hierarchy?<br></div><div><br></div><div>Regards,
Roman<br></div></div></div></div><meta http-equiv="x-dns-prefetch-control" content="on"><br><br> </div> </div> </div></body></html>