Please don't post images of text as they are hard to read, may not display correctly for everyone, and are not searchable.
Instead, paste the text and format it with </> icon or pairs of triple backticks (```), and check the preview window to make sure it's properly formatted before posting it. This makes it more likely that your question will receive a useful answer.
It would be great if you could update your post to solve this.
What is the output of:
GET /
GET /_cat/nodes?v
GET /_cat/health?v
GET /_cat/indices?v
If some outputs are too big, please share them on gist.github.com and link them here.
You might want to add nodes and scale horizontally, honestly you can always reuse different hardware and add more nodes. Elasticsearch is meant to be scalable.
Ok but given the situation do you think increasing the disk and/or memory would resolve these issues?
I'm also planning to add a third node to the cluster.
I'm planning to add a third node to the cluster. I believe this would reduce shards per index which I believe is very critical.
But will this be enough? Do I need to review the whole indexing strategy? I would be happy if I can avoid this because the code is a mess.
PS:
BTW, what do you mean by indexing strategy. Can you provide me a link or resource to study it?
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.