MySQL Behavior Upon Exceeding Memory Cap
jeffreyq
PROOP

4 months ago

Hi there, I currently have a MySQL instance running on a limit of 32GB of Memory. It's been steadily increasing the last week, up to 29GB. I'd like to know what happens when it reaches 32GB. Does it continue to run with degraded performance? Or is it a OOM SIGKILL that would terminate my instance?

Attachments

Solved

3 Replies

4 months ago

Hey, Railway will (OOM) terminate your MySQL service once it has reached/exceeded the memory limit of 32GB.


Status changed to Solved angelo-railway 4 months ago


jeffreyq
PROOP

4 months ago

Got it, thank you. Will it automatically restart?


Status changed to Awaiting Railway Response Railway 4 months ago


4 months ago

Yes, by default Railway uses an "On Failure" restart policy that will automatically restart your service up to 10 times after it crashes from OOM. Since you're on a Pro plan, you can adjust this limit or change the restart policy entirely in your service settings. If all restart attempts are exhausted, the deployment status changes to "Crashed" and you'll receive a notification, at which point you'd need to manually restart it.


Status changed to Awaiting User Response Railway 4 months ago


Railway
BOT

3 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...