Elasticsearch cross cluster does not work as expected


(Satish) #1

Hello,

I have two ES clusters of significant sizes of 4 master nodes per cluster. I have another cluster which is configured as cross between the two clusters. Everything works fine when the ES instances are started afresh. However after sometime my second cluster stops showing results from when queried via the cross cluster. Sometimes it works and quite a few times I get the below error:

$ curl -v -XGET http://10.42.97.15:9400/_remote/info?pretty

  • About to connect() to 10.42.97.15 port 9400 (#0)
  • Trying 10.42.97.15...
  • Connected to 10.42.97.15 (10.42.97.15) port 9400 (#0)

GET /_remote/info?pretty HTTP/1.1
User-Agent: curl/7.29.0
Host: 10.42.97.15:9400
Accept: /

< HTTP/1.1 500 Internal Server Error
< content-type: application/json; charset=UTF-8
< content-length: 360
<
{
"error" : {
"root_cause" : [
{
"type" : "node_disconnected_exception",
"reason" : "[node-es1-1][10.54.181.15:9300][cluster:monitor/nodes/info] disconnected"
}
],
"type" : "node_disconnected_exception",
"reason" : "[node-es1-1][10.54.181.15:9300][cluster:monitor/nodes/info] disconnected"
},
"status" : 500
}

  • Connection #0 to host 10.42.97.15 left intact

The instance is running perfectly fine and I can do a telnet 10.54.181.15 9300 , which shows connected from the same machine I ran the curl command from.

$ telnet 10.54.181.15 9300
Trying 10.54.181.15...
Connected to 10.54.181.15.
Escape character is '^]'.

Is this a bug?


(Satish) #2

I have also opened an issue for this at: https://github.com/elastic/elasticsearch/issues/30247


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.