CrossCluster search using wrong ip address


(Federico Foschini) #1

Hello, I've a local cluster A and a remote elasticsearch B deployed in a docker container.

I would like to use cluster A as a cross cluster search client to search cluster B.

I've configured cluster A in this way:
PUT _cluster/settings
{
"persistent": {
"search": {
"remote": {
"cluster_B": {
"seeds": [
"cluster_B.server.local:9300"
]
}
}
}
}
}

But when I try to query the remote server in elasticsearch.log file on cluster A I found this error:
rg.elasticsearch.transport.ConnectTransportException: [SmKOedA][172.18.0.6:9300] connect_timeout[30s]

It looks like the remote server is pushing it's internal docker ip (172.18.0.6) instead of the one I've configured

Is there a way to fix this behavior?


(Kanagat) #2

hi @Manofwax , what docker images are you use? version?


(Federico Foschini) #3

Hello, I'm using official docker image pinned to version 6.1.4.

This is my elasticsearch.yml file:
cluster.name: "ClusterB
network.host: 0.0.0.0
bootstrap.memory_lock: true
discovery.type: "single-node"
discovery.zen.minimum_master_nodes: 1
search.remote.connect: false

I think the problem is in network.host should I put in there the IP of the phisical machine?


(system) #4

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