First I will apologize for most likely a naive question. I am currently building out our elasticsearch implementation from a single node, to a 3 node cluster. I have followed most of the tutorials I have found on the internet, but it seems my cluster is slower by up to 3x versus the single node we are currently using. When I do a search on our cluster, I see all the drives get pegged to 100% utilization, and the iowait gets up to around 70 on each node. When I do the same query on the single node, I don't even see a hit to the disk, and very little cpu. Here is our current setup in AWS:
The data for the cluster is spread across all 3 nodes, and I mean each node has the complete set of the data. The single node is using all default configuration, but the cluster nodes are just using these added configs:
First I will apologize for most likely a naive question. I am currently
building out our elasticsearch implementation from a single node, to a 3
node cluster. I have followed most of the tutorials I have found on the
internet, but it seems my cluster is slower by up to 3x versus the single
node we are currently using. When I do a search on our cluster, I see all
the drives get pegged to 100% utilization, and the iowait gets up to around
70 on each node. When I do the same query on the single node, I don't even
see a hit to the disk, and very little cpu. Here is our current setup in
AWS:
The data for the cluster is spread across all 3 nodes, and I mean each node
has the complete set of the data. The single node is using all default
configuration, but the cluster nodes are just using these added configs:
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.