From e26058f178cb8a030abfafe79cd0d40f5f235245 Mon Sep 17 00:00:00 2001
From: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Date: Tue, 23 Dec 2025 12:15:12 -0500
Subject: [PATCH] Revise vm.max_map_count recommendation in bootstrap checks

Updated the recommended value for vm.max_map_count to 1048576.
---
 deploy-manage/deploy/self-managed/bootstrap-checks.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deploy-manage/deploy/self-managed/bootstrap-checks.md b/deploy-manage/deploy/self-managed/bootstrap-checks.md
index 4dd35463a1..51cf06420d 100644
--- a/deploy-manage/deploy/self-managed/bootstrap-checks.md
+++ b/deploy-manage/deploy/self-managed/bootstrap-checks.md
@@ -109,7 +109,7 @@ $$$bootstrap-checks-max-map-count$$$
 
 In addition to [unlimited address space](#max-size-virtual-memory-check), to use `mmap` effectively, {{es}} also requires the ability to create many memory-mapped areas. The maximum map count check checks that the kernel allows a process to have at least 262,144 memory-mapped areas and is enforced on Linux only.
 
-To pass the maximum map count check, you must configure `vm.max_map_count` via `sysctl` to be at least `262144`.
+To pass the maximum map count check, you must configure `vm.max_map_count` via `sysctl` to be at least `262144`. The recommended value is `1048576`.
 
 Alternatively, the maximum map count check is only needed if you are using `mmapfs` or `hybridfs` as the [store type](elasticsearch://reference/elasticsearch/index-settings/store.md) for your indices. If you [do not allow](elasticsearch://reference/elasticsearch/index-settings/store.md#allow-mmap) the use of `mmap` then this bootstrap check will not be enforced.
 :::