From 9052286c0bbad7c505e6f66814a8e289032e89a7 Mon Sep 17 00:00:00 2001 From: Jake Howard Date: Thu, 22 Feb 2024 17:27:36 +0000 Subject: [PATCH] Add note for changing Heroku's release dyno type --- .../infrastructure/heroku-release-type.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/notes/infrastructure/heroku-release-type.md diff --git a/docs/notes/infrastructure/heroku-release-type.md b/docs/notes/infrastructure/heroku-release-type.md new file mode 100644 index 0000000..ee8b1ba --- /dev/null +++ b/docs/notes/infrastructure/heroku-release-type.md @@ -0,0 +1,28 @@ +--- +title: Scaling Heroku's release type +tags: + - Heroku +--- + +During `release`, it's possible to consume so much memory, Heroku kills the dyno before it finishes executing. + +``` +heroku[release.xxxx]: Process running mem=1038M(202.8%) +heroku[release.xxxx]: Error R15 (Memory quota vastly exceeded) +heroku[release.xxxx]: Stopping process with SIGKILL +heroku[release.xxxx]: Process exited with status 137 +heroku[release.xxxx]: State changed from up to complete +``` + +When that happens, the release fails (even though it may say "complete"). Whilst it's a good idea not to use huge amounts of memory during release, sometimes it's unavoidable. + +Releases run in a `Standard-1X` dyno, regardless of what the other dynos are set to. This has a 512MB RAM limit, however Heroku will let it push over for short periods. + +Setting the `release` dyno type can't be done from the dashboard, but can be done from the CLI: + +``` +heroku ps:type release=Standard-1X -a +``` + +!!! warning + When running `Eco` or `Basic` dynos, the release container is configured to match. It's not possible to use other types of dyno on these plans.