[DOCS] Use dedicated hosts for ES

[stefnestor]

@jrodewig hello! Our Support team frequently recommends users to reserve a host (e.g. VM) specifically for Elasticsearch & not run other heavy products/services on it. A common on-prem setup topic is choosing to run Kibana, Elasticsearch, Logstash, & Filebeat from one host since "they're all Elastic" (as an egregious example to make the point).

I'm not finding any similar commentary in our ES docs & would like to recommend upon Dev review 🙏🏼

[elasticmachine]

Pinging @elastic/es-docs (Team:Docs)

[elasticmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[jrodewig]

Thanks @stefnestor!

I'd like to get input from someone on @elastic/es-core-infra or @elastic/es-delivery before moving forward with this. The recommendation makes sense to me, but I'm not sure we want to incorporate it as a best practice.

If so, I'll move this somewhere in our installation or configuration docs where it'll be more likely to be seen during setup.

[stefnestor]

Thanks @jrodewig! We completely agree & were speculating both same ballparks :) 🙏🏼

[mark-vieira]

The @elastic/es-perf team might have some input here but I believe the answer is "yes" the expectation is that you run Elasticsearch on a dedicated host, or in a container such that it's resource usage is "isolated". In fact, auto heap size determination is predicated on the fact that available system memory visible to the Elasticsearch process will be for the most part not used by other competing processes.

[danielmitterdorfer]

@mark-vieira is correct. Also, the JVM ergonomically sizes resources (such as GC and JIT compiler threads) based on the assumption that it is the only resource-intensive application on that host (or container).

[jrodewig]

Thanks for the confirmation, everyone. I'll move this over to the setup docs and merge it in.