kumaab opened a new pull request, #1241:
URL: https://github.com/apache/ranger/pull/1241
## What changes were proposed in this pull request?
`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.
## How was this patch tested?
No warnings seen in CI stage: `services-docker-build`
--
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]
