RANGER-5605 : Fix Ranger build failure when triggered through Docker#960
Open
dineshkumar-yadav wants to merge 1 commit into
Open
RANGER-5605 : Fix Ranger build failure when triggered through Docker#960dineshkumar-yadav wants to merge 1 commit into
dineshkumar-yadav wants to merge 1 commit into
Conversation
6d3c34b to
5a3b901
Compare
5a3b901 to
bcf1228
Compare
mneethiraj
approved these changes
May 21, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts JVM/Maven memory settings to prevent Ranger builds from failing due to insufficient heap when building via Docker, and updates documentation/CI configuration accordingly.
Changes:
- Increase Maven JVM max heap for the Docker-based build container and add JVM tuning options.
- Update Docker README to reflect a higher minimum Docker memory allocation.
- Increase Maven JVM max heap in GitHub Actions CI via
MAVEN_OPTS.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| dev-support/ranger-docker/scripts/build/ranger-build.sh | Raises Maven JVM heap and adds additional JVM options for Docker-based builds. |
| dev-support/ranger-docker/README.md | Updates stated minimum Docker memory allocation. |
| .github/workflows/ci.yml | Sets a higher Maven JVM max heap for CI builds. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| fi | ||
|
|
||
| export MAVEN_OPTS="-Xms2g -Xmx2g" | ||
| export MAVEN_OPTS="-Xms512m -Xmx5g -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:SoftRefLRUPolicyMSPerMB=50 ${JAVA_OPTS}" |
|
|
||
| env: | ||
| MAVEN_OPTS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3 | ||
| MAVEN_OPTS: -Xmx5g -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3 |
|
|
||
| env: | ||
| MAVEN_OPTS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3 | ||
| MAVEN_OPTS: -Xmx5g -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3 |
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
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?
Fix Ranger build failure when triggered through Docker
(Please fill in changes proposed in this fix. Create an issue in ASF JIRA before opening a pull request and
set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. RANGER-XXXX: Fix a typo in YYY))
How was this patch tested?
Increased the Maven heap size from 2GB to 5GB (minimum requirement).
Tested the Docker build trigger locally.