honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

No more using 'hybrid mmapfs / niofs' (#25944) 

It looks a bit ambiguous here.

ElasticSearch no more using 'hybrid mmapfs / niofs' which chooses filesystem based on the file. It is any one of the mmapfs, niofs or simplefs depending on the operating system.
As quoted here https://www.elastic.co/guide/en/elasticsearch/reference/5.5/index-modules-store.html

Thanks,
Pulkit Agrawal
This commit is contained in:
propulkit 2017-07-31 13:22:38 +05:30 committed by Adrien Grand
parent 1afc9afcac
commit a2fd1b9f6d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/setup/sysconfig/virtual-memory.asciidoc
View File

@ -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
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