Skip to content

No more using 'hybrid mmapfs / niofs' #25944

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

Merged
merged 1 commit into from
Jul 31, 2017
Merged

No more using 'hybrid mmapfs / niofs' #25944

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/reference/setup/sysconfig/virtual-memory.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
[[vm-max-map-count]]
=== Virtual memory

Elasticsearch uses a <<default_fs,`hybrid mmapfs / niofs`>> directory by
default to store its indices. The default operating system limits on mmap
Elasticsearch uses a <<default_fs,`mmapfs`>> directory by
default for 64bit systems to store its indices. The default operating system limits on mmap
Copy link
Contributor

@jpountz jpountz Jul 28, 2017

Choose a reason for hiding this comment

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

actually we do not support 32-bit systems so I think we can just say we use mmapfs all the time

Copy link
Contributor Author

@propulkit propulkit Jul 29, 2017

Choose a reason for hiding this comment

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

In that case, it will be required to change multiple places. The first will be on index-modules-store
https://www.elastic.co/guide/en/elasticsearch/reference/5.5/index-modules-store.html

Copy link
Contributor

@jpountz jpountz Jul 31, 2017

Choose a reason for hiding this comment

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

This is a good call, I opened #25971. In the meantime I see your PR targets 5.5 where we still support 32-bit systems on a best-effort so I'll merge it as-is and just remove the 64-bit reference when merging to the 6.x/7.x branches.

counts is likely to be too low, which may result in out of memory exceptions.

On Linux, you can increase the limits by running the following command as
Expand Down