Skip to content

Update docker.md readme to note memory requirements#9529

Merged
clintropolis merged 2 commits intoapache:masterfrom
nvolungis:patch-1
Mar 24, 2020
Merged

Update docker.md readme to note memory requirements#9529
clintropolis merged 2 commits intoapache:masterfrom
nvolungis:patch-1

Conversation

@nvolungis
Copy link
Contributor

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 broker process 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:

  • added documentation for new or modified features or behaviors.

Copy link
Contributor

@suneet-s suneet-s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@nvolungis
Copy link
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 docker-compose file unmodified which includes postgres, zookeeper, coordinator, broker, historical router, and middlemanager.

Co-Authored-By: Suneet Saldanha <44787917+suneet-s@users.noreply.github.com>
Copy link
Member

@clintropolis clintropolis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks for the contribution! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants