# org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: Connection error (check network and/or proxy settings)- all nodes failed; tried \[\[172.24.191.234:9010, 172.24.191.231:9010, 172.24.191.233:9010\]\] **URL:** \ **Category:** Elasticsearch\ **Tags:** es-hadoop\ **Created:** [October 4, 2018, 3:11am UTC](https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopnonodesleftexception-connection-error-check-network-and-or-proxy-settings-all-nodes-failed-tried-172-24-191-234-9010-172-24-191-231-9010-172-24-191-233-9010/150957 "2018-10-04T03:11:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![bpaul](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bpaul/32/45225_2.png) [@bpaul](https://discuss.elastic.co/u/bpaul)\ **Post date:** [October 4, 2018, 3:11am UTC](https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopnonodesleftexception-connection-error-check-network-and-or-proxy-settings-all-nodes-failed-tried-172-24-191-234-9010-172-24-191-231-9010-172-24-191-233-9010/150957/1 "2018-10-04T03:11:06Z")
Hello guys, I am trying to export data from hadoop into elastic search. The Map reduce job is getting failed and the daeomon of elastic search is automatically shutting down.I have configured 4 nodes to form an elastic search cluster. Below given are the configuration setting of one node . The configuration parameters are same of other 3 nodes as well. **elasticsearch.yml** node.name: ES\_SLAVE2 node.master: false node.data: true path.data: /das/elasticsearch-2.3.4/data bootstrap.memory\_lock: false xpack.security.enabled: false bootstrap.system\_call\_filter: false action.auto\_create\_index: .security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\* indices.query.bool.max\_clause\_count: 10240 network.host: 172.24.191.233 http.port: 9010 Guys. Let me know if you need any other input. Kindly help ---
**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\ **Post date:** [October 4, 2018, 7:04pm UTC](https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopnonodesleftexception-connection-error-check-network-and-or-proxy-settings-all-nodes-failed-tried-172-24-191-234-9010-172-24-191-231-9010-172-24-191-233-9010/150957/2 "2018-10-04T19:04:00Z")
@bpaul Please avoid double posting in the forums as it creates a lot of noise. > [@bpaul](#): > > the daeomon of Elasticsearch is automatically shutting down. Can you elaborate what you mean by this? Is the Elasticsearch node shutting down or is this the Map Reduce job? If it is the node shutting down, can you provide your node logs? If it is the MR job failing, can you provide the logs from the job? ---
**Author:** ![bpaul](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bpaul/32/45225_2.png) [@bpaul](https://discuss.elastic.co/u/bpaul)\ **Post date:** [October 5, 2018, 6:57am UTC](https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopnonodesleftexception-connection-error-check-network-and-or-proxy-settings-all-nodes-failed-tried-172-24-191-234-9010-172-24-191-231-9010-172-24-191-233-9010/150957/3 "2018-10-05T06:57:28Z")
@james.baiera . Iam glad that you showed up the courtesy to reply. MapReduce job is throwing the above given error and Map reduce job stops after a point of time. The other problem that occured is that the Elastic search Master daemon got down as the error occured. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 2, 2018, 6:57am UTC](https://discuss.elastic.co/t/org-elasticsearch-hadoop-rest-eshadoopnonodesleftexception-connection-error-check-network-and-or-proxy-settings-all-nodes-failed-tried-172-24-191-234-9010-172-24-191-231-9010-172-24-191-233-9010/150957/4 "2018-11-02T06:57:40Z")
Closed on November 2, 2018, 6:57am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.