Skip to content

Commit 734a172

Browse files
authored
Apply suggestions from code review
Signed-off-by: Naarcha-AWS <[email protected]>
1 parent 6f9d0cb commit 734a172

File tree

1 file changed

+2
-1
lines changed
  • _install-and-configure/install-opensearch

1 file changed

+2
-1
lines changed

_install-and-configure/install-opensearch/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,8 @@ The [sample docker-compose.yml]({{site.url}}{{site.baseurl}}/install-and-configu
9898

9999
Sets the size of the Java heap (we recommend half of system RAM).
100100

101-
It's important to note that OpenSearch defaults to `-Xms1g -Xmx1g` for heap memory allocation, which take precedence over configurations specified using percentage notation (`-XX:MinRAMPercentage`, `-XX:MaxRAMPercentage`). For example, if you set `OPENSEARCH_JAVA_OPTS=-XX:MinRAMPercentage=30 -XX:MaxRAMPercentage=70`, the predefined `-Xms1g -Xmx1g` values will override these settings. When using `OPENSEARCH_JAVA_OPTS` to define memory allocation, ensure you use the `-Xms` and `-Xmx` notation.
101+
OpenSearch defaults to `-Xms1g -Xmx1g` for heap memory allocation, which takes precedence over configurations specified using percentage notation (`-XX:MinRAMPercentage`, `-XX:MaxRAMPercentage`). For example, if you set `OPENSEARCH_JAVA_OPTS=-XX:MinRAMPercentage=30 -XX:MaxRAMPercentage=70`, the predefined `-Xms1g -Xmx1g` values will override these settings. When using `OPENSEARCH_JAVA_OPTS` to define memory allocation, make sure you use the `-Xms` and `-Xmx` notation.
102+
{: .note}
102103

103104
- `nofile 65536`
104105

0 commit comments

Comments
 (0)