Skip to content
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

Jump to bottom

Document tuning of vm.max_map_count in deployment guide #660

Closed
schallert opened this issue May 17, 2018 · 2 comments
Closed

Document tuning of vm.max_map_count in deployment guide #660

schallert opened this issue May 17, 2018 · 2 comments
Assignees
@prateek
Labels
area:db All issues pertaining to dbnode C: Storage P: Medium T: Reliability

Comments

@schallert
Copy link
Collaborator

We mmap a lot of files under some circumstances. The kernel parameter vm.max_map_count limits how many mmap areas a process can have open, and defaults to 65536. We should document the impact of this and provide guidance for tuning, maybe in the form of a formula based on number of namespaces, block size, etc. Maybe the host can even warn on boot if the setting is not tuned correctly.
@prateek prateek self-assigned this May 18, 2018
@schallert schallert mentioned this issue Oct 19, 2018
Closed
@schallert
Copy link
Collaborator Author

Can this be closed as of #714?

@richardartoul
Copy link
Contributor

@prateek Can close this when #1118 lands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prateek prateek

Labels
area:db All issues pertaining to dbnode C: Storage P: Medium T: Reliability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prateek @schallert @richardartoul