Skip to content

Conversation

@shainaraskas
Copy link
Contributor

We want to recommend a higher vm.max_map_count for Elasticsearch environments - additional context in issue

What issues does this PR fix?

Part of https://github.com/elastic/docs-content-internal/issues/592

@shainaraskas shainaraskas added the backport-8.16 Automated backport with mergify label Dec 23, 2025
@shainaraskas shainaraskas requested a review from a team as a code owner December 23, 2025 16:56
@shainaraskas shainaraskas added backport-8.17 Automated backport with mergify backport-8.18 Automated backport with mergify backport-8.19 labels Dec 23, 2025
@github-actions
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@github-actions
Copy link

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

@shainaraskas
Copy link
Contributor Author

this page does not exist in previous versions and should be redirected instead. opened an issue for that

https://github.com/elastic/docs-content-internal/issues/615

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

Labels

backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify backport-8.18 Automated backport with mergify backport-8.19

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants