Closed halfofcity closed 5 years ago
Me too. How to resolve it?
me too. 19/04/04 17:14:35 ERROR NetworkClient: Node [10.42.32.93:9200] failed (Connection timed out (Connection timed out)); 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 [[10.42.142.87:9200, 10.42.51.199:9200, 10.42.32.93:9200]] at org.elasticsearch.hadoop.rest.NetworkClient.execute(NetworkClient.java:149)
sometimes this is related to ES_NODES_WAN_ONLY setting in our readme and in elasticsearch-hadoop docs. can you try?
ES_NODES_WAN_ONLY=true works for me,thank you.
@devinsba @shakuzen @zeagord seems everyone asks this and runs into the problem. maybe we switch default from false to true?
hello, @adriancole ES_NODES_WAN_ONLY=true it works. The origin error message is:
ShuffleMapStage 0 (groupBy at ElasticsearchDependenciesJob.java:179) failed in 60.806 s dueto Job aborted due to stage failure: Task 0 in stage 0.0 failed 1 times, most recent failure: Lost task 0.0 in stage 0.0 (TID 0, localhost, executor driver): org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[172.31.117.44:9200]]
172.31.117.44 is the es pod ip , the running job container can connect to the pod ip. (k8s environment). so it is still strange for me. what does env variable 'ES_NODES_WAN_ONLY‘ exactly work for?
es.nodes.wan.only is an elasticsearch feature here are their docs on it.
https://www.elastic.co/guide/en/elasticsearch/hadoop/master/configuration.html
if you need more info I would suggest contacting their support channels as we are not in charge of elasticsearch implementation details.
On Thu, May 30, 2019, 12:22 PM huhu notifications@github.com wrote:
hello, @adriancole https://github.com/adriancole ES_NODES_WAN_ONLY=true it works. The origin error message is:
ShuffleMapStage 0 (groupBy at ElasticsearchDependenciesJob.java:179) failed in 60.806 s dueto Job aborted due to stage failure: Task 0 in stage 0.0 failed 1 times, most recent failure: Lost task 0.0 in stage 0.0 (TID 0, localhost, executor driver): org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried [[172.31.117.44:9200]]
172.31.117.44 is the es pod ip , the running job container can connect to the pod ip. (k8s environment). so it is still strange for me. what does env variable 'ES_NODES_WAN_ONLY‘ work for?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/apache/incubator-zipkin-dependencies/issues/103?email_source=notifications&email_token=AAAPVVYKGR3WV36BBSHNFYDPX5JB7A5CNFSM4E7MH5GKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWRKACY#issuecomment-497197067, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAPVV6JHPQS3JNHLYA22MTPX5JB7ANCNFSM4E7MH5GA .
OK, thanks。 @adriancole
this use 172.18.0.16:9200? but I don't have this.