Skip to content

DOCS-6174 Add vm.max_map_count recommendation to Production Checklist #3260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 9, 2018
Merged

DOCS-6174 Add vm.max_map_count recommendation to Production Checklist #3260

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions source/administration/production-checklist-operations.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,13 +224,15 @@ Linux
- Use ``noatime`` for the :setting:`~storage.dbPath` mount point.

- Configure sufficient file handles (``fs.file-max``), kernel pid
limit (``kernel.pid_max``), and maximum threads per process
(``kernel.threads-max``) for your deployment. For large systems,
limit (``kernel.pid_max``), maximum threads per process
(``kernel.threads-max``), and maximum number of memory map areas per
process (``vm.max_map_count``) for your deployment. For large systems,
the following values provide a good starting point:

- ``fs.file-max`` value of 98000,
- ``kernel.pid_max`` value of 64000, and
- ``kernel.threads-max`` value of 64000
- ``kernel.pid_max`` value of 64000,
- ``kernel.threads-max`` value of 64000, and
- ``vm.max_map_count`` value of 128000

- Ensure that your system has swap space configured. Refer to your
operating system's documentation for details on appropriate sizing.
Expand Down