Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can not connect to the es node, only connect to the bridge ip address

See original GitHub issue

execute command: docker run --rm --name spark-dependencies --env STORAGE=elasticsearch --env ES_NODES=http://172.31.60.138:9200 jaegertracing/spark-dependencies error log shows:

ERROR NetworkClient: Node [172.18.0.1:9200] failed (Connection refused (Connection refused)); no other nodes left - aborting...
Exception in thread "main" org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[172.18.0.1:9200]]

Is that a bug?

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:23 (12 by maintainers)

Top GitHub Comments

1reaction

pavolloffaycommented, Dec 12, 2019

Yes we know this behaviour, it’s always better to specify the ports.

0reactions

pavolloffaycommented, Dec 12, 2019

From readme in this repository

* `ES_NODES`: A comma separated list of elasticsearch hosts advertising http. Defaults to
              localhost. Add port section if not listening on port 9200. Only one of these hosts
              needs to be available to fetch the remaining nodes in the cluster. It is
              recommended to set this to all the master nodes of the cluster. Use url format for
              SSL. For example, "https://yourhost:8888"