Migrations causing app to run out of memory

I currently have a few pretty hefty migrations (with percolate:migrations) queued up and when I test them on my staging server it manages to eat up all the memory (512M) and crash the container. I run Migrations.migrateTo(‘latest’) in my startup on the server.

2017-03-01 12:54:28+01:00Application exited with code: null signal: SIGKILL
2017-03-01 12:54:28+01:00Application process closed with code: null signal: SIGKILL
2017-03-01 12:54:34+01:00The container has run out of memory. A new container will be started to replace it.

Is there a way to garbage collect manually in between each step of the migration ?

I guess my work-around for now will be to switch off the server for maintenance and then run migration from my local machine and then fire it up again.

1 Like