Thanks Aaron, It's probably a network/firewall issue. I'll try to fiddle around to what's going on.
On Thu, Nov 3, 2016 at 7:42 PM, Aaron Niskodé-Dossett <doss...@gmail.com> wrote: > Oh, interesting. I believe that's the same error I saw when I tried to > run the Storm bolt (which only support 1.X) against a 2.X server. Sorry, > other than that I'm not sure what could be causing your problem. > > On Thu, Nov 3, 2016 at 12:39 PM Mostafa Gomaa <mgo...@trendak.com> wrote: > >> Hi Aaron, >> >> Thanks for the response. I am actually using the bolt you linked me to. >> Any ideas? >> >> On Thu, Nov 3, 2016 at 7:36 PM, Aaron Niskodé-Dossett <doss...@gmail.com> >> wrote: >> >> Hi Mostafa Gomaa -- Unfortunately Storm's bolt does not support Elastic >> 2.X. There is a PR to add this support, which I need to put some work >> into. In the meantime, you could try elastic's bolt ( >> https://www.elastic.co/guide/en/elasticsearch/hadoop/current/storm.html). >> >> Thanks, Aaron >> >> On Thu, Nov 3, 2016 at 11:30 AM Mostafa Gomaa <mgo...@trendak.com> wrote: >> >> >> I am currently using apache storm 1.0.2 with elasticsearch 2.2.1 and >> using the elasticsearch bolt to write some data. >> The machines are on microsoft azure environment, and the ES bolt is >> giving me this error >> java.lang.RuntimeException: >> org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException: >> Connection error (check network and/or proxy settings)- all nodes failed; >> tried [[127.0.0.1:9200]] >> my current configurations doesn't include localhost as elasticsearch node >> but it keep saying that it tried localhost, and the thing is that i can >> curl the elasticsearch node from the storm machine's terminal and it can be >> accessed >> >> >>
