[Fix] Remove ARM-specific JVM options from Elasticsearch configuration#191
Merged
JonnyTran merged 2 commits intoExtralit:developfrom Feb 12, 2026
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Removes an ARM-specific JVM flag from the root docker-compose.yaml Elasticsearch service to prevent JVM startup failure on Windows/x86 hosts, and records the fix in the server changelog for the upcoming release.
Changes:
- Removed
-XX:UseSVE=0from Elasticsearch JVM options indocker-compose.yaml. - Added a corresponding entry to
extralit-server/CHANGELOG.mdunder Fixed.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| extralit-server/CHANGELOG.md | Documents the Elasticsearch startup fix for Windows/x86 in the Unreleased changelog. |
| docker-compose.yaml | Removes the incompatible ARM-only JVM option from Elasticsearch environment configuration. |
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.
PR Title:
[Fix] Remove ARM-specific JVM options from Elasticsearch configuration
Description
This PR fixes the Elasticsearch container startup failure on Windows/x86 systems by removing ARM-specific JVM options that are not compatible with x86 architectures.
The
-XX:UseSVE=0JVM flag (which disables ARM's Scalable Vector Extension) was causing the following error on Windows and x86 Linux systems:Unrecognized VM option 'UseSVE=0'
Error: Could not create the Java Virtual Machine.
This makes it work on all system architectures.
Related Tickets & Documents
Closes #187
What type of PR is this? (check all applicable)
Steps to QA
docker-compose downto stop existing containers(if not already deployed)docker-compose up -d elasticsearchto start Elasticsearch(can also run whole app but check for elasticsearch errors)docker logs extralit-elasticsearch-1Added/updated tests?
Added/updated documentations?
Checklist