RANGER-5775: update docker setup for low footprint of Ranger services, 256mb by default - #1198
Open
mneethiraj wants to merge 1 commit into
Open
RANGER-5775: update docker setup for low footprint of Ranger services, 256mb by default#1198mneethiraj wants to merge 1 commit into
mneethiraj wants to merge 1 commit into
Conversation
…, 256mb by default
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
1 participant
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.
What changes were proposed in this pull request?
Reduced memory use for Ranger core Docker containers by standardizing on 256 MB JVM heap per service (configurable via
.env).added per-service RANGER_*_MAX_HEAP variables in
.env(admin, usersync, tagsync, pdp, kms, audit ingestor/dispatcher).docker-compose passes these env vars into each container
updated service start scripts to read heap from env when set; otherwise keep existing defaults (1g for core services)
optional metaspace tuning via RANGER_JVM_METASPACE / RANGER_JVM_MAX_METASPACE
How was this patch tested?
Verified that all Ranger services startup successfully with 256mb max-heap.