wiquan opened a new pull request, #12963: URL: https://github.com/apache/druid/pull/12963
## Fixes #10331 - Fresh Docker install results in "Uh... I have no servers. Not assigning anything..." ### Description The docker-compose.yml file uses hardcoded 'conf/druid/single-server' configurations. This results in OOM killed broker as described in [Issue#10331](https://github.com/apache/druid/issues/10331). The suggestion was: > Maybe we should update the docker-compose settings to use either the "nano" or "micro" settings from https://druid.apache.org/docs/latest/operations/single-server.html. (Or have two docker-compose config bundles, one for "nano" and one for "micro".) That would probably help. A PR to do that would be great. This was the goal of this PR. The change was to include a new env var **DRUID_SINGLE_NODE_CONF** that takes a value from the list: - large - medium - micro-quickstart - nano-quickstart - small - xlarge This would get injected into the container via docker-compose env vars. Since I use this on my Mac M1, I have modified environment file to specify 'DRUID_SINGLE_NODE_CONF=micro-quickstart' . An example modified environment file is part of this PR. #### Fixed the bug Since docker-compose files are typically for local development it made sense to use the smaller memory profiles. I also create a multi-arch Docker image with buildx for my Mac M1 with support for: - linux/amd64 - linux/arm64 This can be provided if needed. ##### Key changed/added classes in this PR * `druid.sh` new shell functions for conf path resolution <hr> This PR has: - [x] been self-reviewed. - [x] added documentation for new or modified features or behaviors. - [x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader. - [x] been tested in a test Druid cluster. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
