When the node1's queue length up, node 2's down. And then reverse. They are go through the rule in these days.
The search requests to each node is similar.
I feel confuse to the queue length's performance.Is there some explanation about that?
If you are using something that leverages the transport or node client, or any of our officially provided clients then it will automatically round robin, producing this behaviour.
We use Jmeter for load testing. The test case open 200 threads to send HTTP requests to our cluster.
We also try another test case: open 200 threads to keep sending HTTP requests to only node 1. In this case, two nodes in the cluster got busy and the queue length still acted in that behavior. It seen like search request can be redirect between two nodes. Is that what you said "transport"?
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.