Conversation
…CE variables
RANGER_JVM_METASPACE and RANGER_JVM_MAX_METASPACE are documented in
dev-support/ranger-docker/.env as optional tuning knobs and are left
commented out, so the services fall back to the upstream defaults
(100m / 200m). docker-compose.ranger-audit-service.yml interpolated them
as ${RANGER_JVM_METASPACE} without a default, so every compose
invocation printed:
level=warning msg="The \"RANGER_JVM_METASPACE\" variable is not set.
Defaulting to a blank string."
Ten such warnings appeared on each CI run (5 per variable: the
audit-ingestor service, the x-audit-dispatcher-env-common anchor and the
three dispatcher services that merge it).
The other compose files pass these variables through with the list form
(- RANGER_JVM_METASPACE), which does not interpolate and therefore does
not warn. Use ${VAR:-} here so the optional-knob semantics are kept
without the warning. Verified that "docker compose config" output is
byte-identical before and after, for both the core and the plugin stacks
used by CI, and that both now run with zero warnings.
mneethiraj
approved these changes
Sep 20, 2026
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
2 participants
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?
RANGER_JVM_METASPACEandRANGER_JVM_MAX_METASPACEare documented indev-support/ranger-docker/.envas optional tuning knobs and are left commented out, so the services fall back to the upstream defaults (100m / 200m).docker-compose.ranger-audit-service.ymlinterpolated them as${RANGER_JVM_METASPACE}without a default, so every compose invocation printed:level=warning msg="The "RANGER_JVM_METASPACE" variable is not set.
Defaulting to a blank string."
Ten such warnings appeared on each CI run (5 per variable: the audit-ingestor service, the x-audit-dispatcher-env-common anchor and the three dispatcher services that merge it).
The other compose files pass these variables through with the list form (- RANGER_JVM_METASPACE), which does not interpolate and therefore does not warn. Use ${VAR:-} here so the optional-knob semantics are kept without the warning.
How was this patch tested?
No warnings seen in CI stage:
services-docker-build: https://github.com/kumaab/ranger/actions/runs/35481593938/job/106003841221