Update docker.md readme to note memory requirements#9529
Merged
clintropolis merged 2 commits intoapache:masterfrom Mar 24, 2020
Merged
Update docker.md readme to note memory requirements#9529clintropolis merged 2 commits intoapache:masterfrom
clintropolis merged 2 commits intoapache:masterfrom
Conversation
suneet-s
approved these changes
Mar 17, 2020
Contributor
suneet-s
left a comment
There was a problem hiding this comment.
Thanks for the pointer about error code 137! The integration tests need 4Gb to run.
What size cluster were you trying to start that it needed 6?
Contributor
Author
|
@suneet-s I was able to run just the broker consistently with 4gb. The whole cluster also runs with 4, but crashed occasionally. 6 seems to be the floor for consistency, at least on my machine. Perhaps noting a range of 4-6 would be more appropriate so people don't overshoot if unnecessary. I'm running the cluster described in the |
suneet-s
reviewed
Mar 17, 2020
Co-Authored-By: Suneet Saldanha <44787917+suneet-s@users.noreply.github.com>
clintropolis
approved these changes
Mar 24, 2020
Member
clintropolis
left a comment
There was a problem hiding this comment.
lgtm, thanks for the contribution! 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
When attempting to get druid running inside Docker Desktop via the docker-compose file (both built from source and referencing the 0.17.0 published image), I experienced repeated crashing of the
brokerprocess with a 137 error code. 137 indicates an OOM error, so I notched up Docker's memory resource in 1gb increments (I believe the default is 2gb), landing on 6gb as a setting that works reliably.As a newcomer with little knowledge of druid, it was quite difficult to identify exactly what the issue was initially. A note like this would have helped point me in the right direction.
This PR has: