Skip to content

Change vm.max_map_count default to 1048576 in All ES docs for version 8.16+ #4295

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.

Sign up for GitHub

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

Open
kunisen wants to merge 3 commits into
base: main
Choose a base branch
from
+5 −1
Open

Change vm.max_map_count default to 1048576 in All ES docs for version 8.16+ #4295

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aa96c2d
Update vm-max-map-count.md
kunisen Dec 11, 2025
49127e1
Update deploy-manage/deploy/self-managed/vm-max-map-count.md
kunisen Dec 11, 2025
9271828
Update deploy-manage/deploy/self-managed/vm-max-map-count.md
kunisen Dec 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion deploy-manage/deploy/self-managed/vm-max-map-count.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,14 @@ products:

{{es}} uses a [`mmapfs`](elasticsearch://reference/elasticsearch/index-settings/store.md#mmapfs) directory by default to store its indices. The default operating system limits on mmap counts is likely to be too low, which may result in out of memory exceptions.
Copy link

@lkts lkts Dec 11, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

We say here "The default operating system limits on mmap counts is likely to be too low" but that is no longer true. I think your addition below supersedes this statement and we can remove it.

Copy link

@lkts lkts Dec 11, 2025

Choose a reason for hiding this comment

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

Maybe we want to say "could be too low"?


:::{admonition} Verify `vm.max_map_count` configuration
Copy link
Contributor

@yetanothertw yetanothertw Dec 11, 2025

Choose a reason for hiding this comment

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

Suggested change
:::{admonition} Verify `vm.max_map_count` configuration
:::{admonition} Verify vm.max_map_count configuration

Thanks for spotting this @kunisen -- I missed it!

I think we should go with option B (as described in your comment).

If the operating system's default `vm.max_map_count` value is `1048576` or higher, no configuration change is necessary. If the default value is lower than `1048576`, configure the `vm.max_map_count` parameter to `1048576`.
:::

On Linux, you can increase the limits by running the following command as `root`:

```sh
sysctl -w vm.max_map_count=262144
sysctl -w vm.max_map_count=1048576
```

To set this value permanently, update the `vm.max_map_count` setting in `/etc/sysctl.conf`. To verify after rebooting, run `sysctl vm.max_map_count`.
Expand Down
Loading