The idea is to use some nodes with enough resources to perform analysis (heavy aggregations) leaving unloaded other nodes used for data collection and light searches.
It's the exact opposite of Configure Kibana for multiple ES servers/nodes.
Elasticsearch has created a special node type: "client node", which contains "no data", and cannot become a "master node". The client node's function is to perform the final resource heavy merge-sort at the end of the query.
and dont use master as client to kibana !
Hello @saif,
thank you very much, I'll try this solution right away.
I checked the Elasticsearch docs before opening this topic but I didn't find comprehensive info about nodes attributes and their usage, do you have any link about this topic?
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.