OpenSearch running on Dockers

Solved438 viewsDocker indexing engine opensearch
0
9 Comments

Hi Dojo,

I would like to connect an OpenSearch cluster running on Dockers, but I always have the same error:

OpenSearch.Net.OpenSearchClientException: Maximum number of retries reached, failed over to all the known alive nodes before failing. Call: unknown resource ---> OpenSearch.Net.PipelineException: Failed sniffing cluster state. ---> System.AggregateException: One or more errors occurred. ---> OpenSearch.Net.PipelineException: An error occurred trying to read the response from the specified node. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond IPNode:9200

I have two dockers running, 1 per node. DB.xml is linked to server which contains the dockers. I think that problem should be on docker-compose.yml or opensearch.yml from cluster.

Does OpenSearch dockers supported by DM? If yes, which is the best configuration on cluster?

Thanks!

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 31st May 2024
Robbe De Ghein [SLC] [DevOps Advocate] commented

Hi Daniel, are you running the docker container in Windows Subsystem for Linux (WSL)?
Daniel Martinez [DevOps Enabler] commented

Hello Robbe, no. Everything is running on Linux.
Robbe De Ghein [SLC] [DevOps Advocate] commented

Did you configure “network.publish_host” to anything?
Daniel Martinez [DevOps Enabler] commented

Yes, Robbe. Do you know if containers need an extra network configuration? Maybe the problem is on communication between both container nodes.
Robbe De Ghein [SLC] [DevOps Advocate] commented

I believe this is a problem with the network configuration, but it’s hard to say exactly without knowing anything about your configuration.

I think that the nodes are trying to sniff the cluster configuration but hitting timeouts due to it binding to the internal & local ip inside the docker container instead of to the exposed IP which is reachable from outside the container.

What did you set the “network.publish_host” to?
Show 4 more comments

1 Answer

0
4.66K 1 Comment

Hi Daniel,
Have you been able to solve this based on the comments above? If yes, could you select this answer to indicate that this question can be closed?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 31st May 2024
Daniel Martinez [DevOps Enabler] commented

Hi Marieke,
Finally we decided to use a different architecture to run OpenSearch. So you can close this question.
Regards!
You are viewing 1 out of 1 answers, click here to view all answers.