Choosing an Erlang Supervisor Restart Strategy for Stateful Workers
Use one_for_one for independent stateful gen_servers, pair it with caller timeouts, and verify fresh state after a kill.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use one_for_one for independent stateful gen_servers, pair it with caller timeouts, and verify fresh state after a kill.
A technical guide on choosing between ETS and Mnesia for Erlang state management, comparing performance, durability, and distribution with a hybrid implementation example.
Upgrade a running Erlang OTP node to a newer release without downtime using release_handler. Follow the step‑by‑step guide to prepare, execute, verify, and roll back if needed.
Match Erlang OTP restart strategies to your failure domain so a crashing worker does not restart unrelated services.
Erlang's async message passing relies on per-process mailboxes managed by the BEAM VM. Understand selective receive, unbounded mailbox risks, and practical diagnostics.
A practical diagnostic guide for Erlang OTP supervisor crash loops: recognize the restart intensity pattern, map symptoms to causes, run ordered checks, apply fixes tied to findings, and know when escalation is correct.
Learn how to update an Erlang/OTP application on a live node using release_handler, appup files, and OTP’s built‑in rollback. Follow a step‑by‑step guide, verify the upgrade, and recover if something goes wrong.
Learn how the one_for_one restart strategy isolates failures in Erlang OTP supervision trees, see a concrete gen_server example, and understand when to use it.
A practical diagnostic guide for Erlang/OTP clusters where nodes show nodedown or net_kernel:connect_node timeouts. Covers cookie, EPMD, name resolution, firewall and version checks with matched fixes.