Very often, we get so that all new indices converge on one node and the node starts to reject.
Now we use ILM and each index is given a priority.
I want to configure so that indexes with equal priority are placed evenly across all servers.
For example now:
This is the number of indexes of the same priority that are written to for each server.
343 ess04
353 ess07
527 ess02
531 ess03
568 ess06
This is the number of indexes of the same priority that are written to for each node.
If you are referring to index.priority this relates to recovery only, as per the docs. Elasticsearch balances indices based on the shard count on each node, followed by how much disk space the nodes have.
I just don't know how else to find the indexes that are currently being logged when using data-stream, I have the highest index.priority in the hot phase, after the rollover the warm phase immediately follows.
All nodes have the same roles. The task is to distribute all the indexes in which the record is made evenly throughout the cluster.
I want to know how people do balancing, I thought the developers could tell me how to solve this problem.
Maybe someone has already encountered this problem and solved it.
Your last lot of numbers show that the node you are concerned about has pretty much the same number of shards as all the other nodes, that is how Elasticsearch balances things.
Are you seeing all shards for a new index being allocated on a single node?
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.