Which upgrade path preserves state for a small Erlang app during zero‑downtime migration?
Goal Upgrade a lightweight OTP application in a production cluster while keeping all nodes online. Constraints Stateful gen_server modules must survive the code change, dependencies must be pinned to avoid mismatched BEAM images, and the upgrade path must be reproducible. Unresolved Decision OTP’s release_handler offers a standard --upgrade workflow but its