repos/notes
1
Fork 0
mirror of https://github.com/RealOrangeOne/notes.git synced 2024-12-22 02:55:58 +00:00
Code Activity

Add note for changing Heroku's release dyno type

Browse source
This commit is contained in:
Jake Howard 2024-02-22 17:27:36 +00:00
parent b07249f7ae
commit 9052286c0b
Signed by: jake
GPG key ID: 57AFB45680EDD477
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
docs/notes/infrastructure/heroku-release-type.md Normal file
View file

@ -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 <app>
```
!!! 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.