bump recommended max map count to 3 million (#1297)

m3db · Jan 16, 2019 · 3fff6ca · 3fff6ca
1 parent 713314a
commit 3fff6ca
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/operational_guide/kernel_configuration.md b/docs/operational_guide/kernel_configuration.md
@@ -4,11 +4,11 @@ Kernel Configuration
 This document lists the Kernel tweaks M3DB needs to run well.
 
 ## vm.max_map_count
-M3DB uses a lot of mmap-ed files for performance, as a result, you might need to bump `vm.max_map_count`. We suggest setting this value to `262144`, so you don’t have to come back and debug issues later.
+M3DB uses a lot of mmap-ed files for performance, as a result, you might need to bump `vm.max_map_count`. We suggest setting this value to `3000000`, so you don’t have to come back and debug issues later.
 
 On Linux, you can increase the limits by running the following command as root:
 ```
-sysctl -w vm.max_map_count=262144
+sysctl -w vm.max_map_count=3000000
 ```
 
 To set this value permanently, update the `vm.max_map_count` setting in `/etc/sysctl.conf`.

diff --git a/src/dbnode/server/limits.go b/src/dbnode/server/limits.go
@@ -30,7 +30,7 @@ import (
 const (
 	// TODO: determine these values based on topology/namespace configuration.
 	minNoFile     = 500000
-	minVMMapCount = 262144
+	minVMMapCount = 3000000
 	maxSwappiness = 1
 )