From 4d298d9ae4c1043a63095517c365f11a82bcb229 Mon Sep 17 00:00:00 2001 From: Joe Ferguson Date: Mon, 19 Dec 2016 11:15:41 -0800 Subject: [PATCH] Add upstream quote about elastic 5.x vm.max_map_count check --- elasticsearch/content.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/elasticsearch/content.md b/elasticsearch/content.md index 4ad9e6e61759..42d963a79d1a 100644 --- a/elasticsearch/content.md +++ b/elasticsearch/content.md @@ -21,6 +21,10 @@ See the following sections of the upstream documentation for more information: - [Setup Elasticsearch » Important System Configuration » Virtual memory](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/vm-max-map-count.html) - [Setup Elasticsearch » Bootstrap Checks » Maximum map count check](https://www.elastic.co/guide/en/elasticsearch/reference/5.0/_maximum_map_count_check.html) +This [comment in elastic/elasticsearch#4978](https://github.com/elastic/elasticsearch/issues/4978#issuecomment-258676104) shows why this change was added in upstream. Production mode is when listening on non-localhost. + +> Elasticsearch will not start in production mode if `vm.max_map_count` is not high enough. [...] If the value on your system is NOT high enough, then your cluster is going to crash and burn at some stage and you will lose data. + ## Running Containers You can run the default `elasticsearch` command simply: