i have 3 indices in the cluster that are read-heavy and the load on the nodes on which the shards of these indices are located is very high (the indexes are small, the largest index weighs 5 gigabytes)
we are thinking to provision a separate cluster for them
what do you do in such cases? or is it better to add more nodes to the existing cluster and label them as hot (sorry, not strong in elastic terminology) and schedule these indexes on them
but I see only 1 plus for this approach (do not provision additional cluster), but for the rest, the load will still go to the control plane (the same masters, all sorts of coordinator and ingest nodes)
It seems to me that it's still easier to provision separate cluster, or am I wrong?
Thanks in advance to everyone for the replies!
That is not ideal, you have no redundancy if you lose that master node and your cluster will be unavailable.
Otherwise if your index is small and you have decent hardware support, we might need more info on why you think you have heavy read loads. Things like mappings, queries, query rates, logs etc.
It's certainly much easier to manage one cluster, and I don't think it makes much difference in terms of performance because ...
... this reasoning is unsound. Master nodes and ingest nodes are not involved in searches, and you can scale searches horizontally a very long way within a single cluster.
@DavidTurner
Okay, so for example i have cluster of 5 nodes, and 1 index that has very intensive reads, so it can slow down all other indexes ( in terms of using Harware ) so i need to label this node as hot and migrate all shards to this nodes right?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
any ideas? thank you