3 months ago
I tried increasing my memory limit from 8gb -> 16gb and it won't apply.
First I attempted it in the UI and clicked deploy. It shows up in my settings as 16gb but the metrics still have it limited to 8gb.
I noticed when I clicked deploy it didn't actually redeploy - it just updated the settings UI as if it deployed and applied. So I tried manually re-deploying but it's still stuck at 8gb. (I tried this a few times with different memory configs to make sure it wasn't transient and its still pinned to 8gb).
I also tried to use the CLI environment edit with the config deploy.limitOverride.containers.memoryBytes 16000000000 and redeployed via the CLI but it didn't apply the change either.
13 Replies
3 months ago
I'm confused, that service is set to 16gb?
Yes but the limit isnt updating
Attachments
The settings show 16gb, but the limit is not updating even if i redeploy.
Attachments
3 months ago
Have you redeployed?
3 months ago
Please do
Still limited to 8
Attachments
3 months ago
Do you have a railway.json that may be overriding this?
3 months ago
I believe the UI does warn you, but best to check anyways.
In this case no i created the Postgres in the UI it's not managed by git or anything
3 months ago
If it were me, and this is just me and am not explicitly recommending this (esp if you can't afford downtime), I would change the region of the service and then change it back.
3 months ago
Just a naggling feeling that it might give things a nudge.