I'm doing consultant work for a large government organization that need
some guidelines for how to set up ElasticSearch or Solr for their projects.
One topic that has surfaced several times is the validity in running
several ES instances per node. The use-case is that several smaller
projects (about 10-15)
need access to a search cluster with replication and redundancy, so I'm
guessing that a cluster size of 3-4 nodes will be typical. The argument for
running several instances per node vs having multiple indices per instance
is that each project gets more "control" over the environment during events
such as full
cluster restarts or version upgrades.
However, I have read that the ES team does not recommend running multiple
instances per node unless you have tons of memory (to preserve compressed
It would be very helpful to know the reasoning behind this, so why is
running multiple instances not recommended?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.