Set memory limit on server's docker containers #468
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We were running into issues where the docker containers were increasing the memory usage over time until after a couple of days taking too much memory from the server which causes the server to throttle and respond very slowly until eventually going down.
Details
By adding a memory limit, docker will kill the container when it gets to the limit of memory usage and the docker container will be restarted – as its started up with the
--restart unless-stopped
option.However, we need to add the logic for cleaning the
server.pid
if exists when starting the server given that when the docker container starts itself after being killed it runs into an error when starting the server as theserver.pid
already exists: