Does release_handler:rollback/1 guarantee consistency after a failed OTP upgrade?
Goal Determine whether release_handler:rollback/1 can safely return a running Erlang node to the previous release after an upgrade fails partway through activation. Constraints and uncertainty Assuming a standard OTP release with release_handler and relup support, the upgrade may already have loaded new modules and migrated some processes while other nodes o
erlang