I had debugging this problem for so long time now. I tweaked every relevant
setting but just cannot get it to work. I really hope someone with
knowledge about Elasticsearch networking can give me some help.
So I got two machines in the same data-center, but communicate to each
other by public ip. (network.publish_host is set)
The symptoms are:
1: Cluster health is green showing 2 nodes
2: When the slave node initially started, all queries are fine. After some
time, query would not work unless adding "preference=_local". This is true
for HTTP curl for both machine.
3: When I shut down the slave node, soon the master node would work fine
without the "_local" suffix.
No special error is shown.
Please feel free to share any ideas you have about this case.
you should check your logfiles on each of the nodes. Maybe they
disconnected from each other (and reconnect all the time), so that you get
problems when you execute your requests round robin. Using curl from one
node to another does not show any problems? They are reachable all the time
(at low latency)?
I had debugging this problem for so long time now. I tweaked every
relevant setting but just cannot get it to work. I really hope someone with
knowledge about Elasticsearch networking can give me some help.
So I got two machines in the same data-center, but communicate to each
other by public ip. (network.publish_host is set)
The symptoms are:
1: Cluster health is green showing 2 nodes
2: When the slave node initially started, all queries are fine. After some
time, query would not work unless adding "preference=_local". This is true
for HTTP curl for both machine.
3: When I shut down the slave node, soon the master node would work fine
without the "_local" suffix.
No special error is shown.
Please feel free to share any ideas you have about this case.
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.