From a2fd1b9f6dbd289d20cc151432f30f741b3b20f5 Mon Sep 17 00:00:00 2001 From: propulkit Date: Mon, 31 Jul 2017 13:22:38 +0530 Subject: [PATCH] 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 --- docs/reference/setup/sysconfig/virtual-memory.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/setup/sysconfig/virtual-memory.asciidoc b/docs/reference/setup/sysconfig/virtual-memory.asciidoc index b9b97a6e2d6..ac654c9b020 100644 --- a/docs/reference/setup/sysconfig/virtual-memory.asciidoc +++ b/docs/reference/setup/sysconfig/virtual-memory.asciidoc @@ -1,8 +1,8 @@ [[vm-max-map-count]] === Virtual memory -Elasticsearch uses a <> directory by -default to store its indices. The default operating system limits on mmap +Elasticsearch uses a <> 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