Skip to content

fix: correct JVM options syntax for ELASTIC_MEMORY_SIZE #610

Description

Description

The .env sample currently uses an uppercase G when specifying JVM heap settings via OPENSEARCH_JAVA_OPTS (for example, -Xms1G -Xmx1G).

ELASTIC_MEMORY_SIZE=4G

The official OpenSearch and Elasticsearch documentation consistently uses lowercase g (for example, -Xms1g -Xmx1g).

While both formats are accepted by the JVM, aligning the documentation with the examples used in OpenSearch and Elasticsearch would improve consistency and reduce confusion for users.

References:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugType: something isn't working (fix:).needs triageNeeds triage from the Filigran product team.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions