From 15342c4dd2ed24f7e7b9d6ecdb4f44f650e9af68 Mon Sep 17 00:00:00 2001 From: Xiang Dai <764524258@qq.com> Date: Wed, 27 Nov 2019 22:39:34 +0800 Subject: [PATCH] [DOCS] Clarify how to update max memory size in bootstrap checks (#48975) --- docs/reference/setup/bootstrap-checks.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/setup/bootstrap-checks.asciidoc b/docs/reference/setup/bootstrap-checks.asciidoc index 83209cbf3b8..f65526eb361 100644 --- a/docs/reference/setup/bootstrap-checks.asciidoc +++ b/docs/reference/setup/bootstrap-checks.asciidoc @@ -143,9 +143,9 @@ maximum size virtual memory check enforces that the Elasticsearch process has unlimited address space and is enforced only on Linux. To pass the maximum size virtual memory check, you must configure your system to allow the Elasticsearch process the ability to have unlimited -address space. This can be done via `/etc/security/limits.conf` using -the `as` setting to `unlimited` (note that you might have to increase -the limits for the `root` user too). +address space. This can be done via adding ` - as unlimited` +to `/etc/security/limits.conf`. This may require you to increase the limits +for the `root` user too. === Maximum map count check