Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to use 50 percent memory as heap #23

Merged
merged 3 commits into from
May 3, 2023
Merged

Add option to use 50 percent memory as heap #23

merged 3 commits into from
May 3, 2023

Conversation

rishabh6788
Copy link
Collaborator

Description

Adds option to use 50 percent memory as heap. This change is in-line with recommended best practice of using 50% memory as heap and not to exceed 32G. This is an optional flag which means if not explicitly set the OS process would use the default 1G heap size.

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

README.md Outdated
@@ -58,7 +58,7 @@ In order to deploy both the stacks the user needs to provide a set of required a
| account (Optional) | string | User provided aws account |
| dataNodeStorage (Optional) | string | User provided ebs block storage size, defaults to 100Gb |
| mlNodeStorage (Optional) | string | User provided ebs block storage size, defaults to 100Gb |
| jvmHeapSize (Optional) | integer | User provided JVM heap memory size (integer) in Gb, defaults to 1Gb, e.g. `--context jvmHeapSize=2` to set heap to 2Gb |
| use50PercentHeap (Optional) | boolean | Boolean flag to use 50% of physical memory as heap. e.g., `--context use50PercentHeap=true` |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add what is the default? If it is present by default do we need to add this param just to disable it?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default is 1G that comes pre-configured in opensearch.yml that should not be disabled. Will add it in the README

Signed-off-by: Rishabh Singh <sngri@amazon.com>
@opensearch-trigger-bot
Copy link

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.x 1.x
# Navigate to the new working tree
pushd ../.worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-23-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d3b12a8774835f1a6fdf41d2ea00b8e9fb7f8b8e
# Push it to GitHub
git push --set-upstream origin backport/backport-23-to-1.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-23-to-1.x.

rishabh6788 added a commit that referenced this pull request Oct 24, 2023
Signed-off-by: Rishabh Singh <sngri@amazon.com>
(cherry picked from commit d3b12a8)
rishabh6788 added a commit that referenced this pull request Oct 24, 2023
Signed-off-by: Rishabh Singh <rishabhksingh@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants