MySQL Bug triggers huge memory allocation with high open file limit #47
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.
On some systems (for example ArchLinux) there is by default a large open file limit configured. MySQL 5.7 has a bug that triggers it to allocate a lot of RAM at startup (more than 16 GB!). This bug was fixed in later versions of MySQL. As a workaround the problem can be avoided by adding small ulimits in the docker-compose file which I have done in this commit.
For more information see here: https://bugs.mysql.com/bug.php?id=96525 and docker-library/mysql#579.