I have set private ip of my data node. discovery.zen.ping.unicast.hosts: ["10.142.181.16"] and have disabled the multicast
discovery.zen.ping.multicast.enabled: false Regards Geet On Fri, Mar 21, 2014 at 2:17 PM, David Pilato <da...@pilato.fr> wrote: > status is incorrect but I guess it's due to the fact your data node is not > a master node and can't find a master. > > How did you set unicast? > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/elasticsearchfr> > > > Le 21 mars 2014 à 09:33:35, Geet Gangwar (geetgang...@gmail.com) a écrit: > > Thanks David for such a quick reply. > > I tried you command from one node to second node and got following result. > > { > "status" : 503, > "name" : "cleandata-DataNode-1", > "version" : { > "number" : "1.0.1", > "build_hash" : "5c03844e1978e5cc924dab2a423dc63ce881c42b", > "build_timestamp" : "2014-02-25T15:52:53Z", > "build_snapshot" : false, > "lucene_version" : "4.6" > }, > "tagline" : "You Know, for Search" > } > > Dont know whehter it is correct or something is wrong. > > Regards > > Geet > > > On Fri, Mar 21, 2014 at 12:43 PM, David Pilato <da...@pilato.fr> wrote: > >> They are sharing same security group name and are deployed in same >> region? >> If unicast does not work using private IP, aws plugin won't work either. >> >> Can you from one node run >> >> curl http://secondnodeip:9200/ >> >> Same from second node. >> >> >> -- >> David ;-) >> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs >> >> >> Le 21 mars 2014 à 08:08, Geet Gangwar <geetgang...@gmail.com> a écrit : >> >> Hi >> >> I am also facing same issue of no dicovery.ec2 logs getting generated for >> elasticsearch 1.0.1 and cloud-aws plugin 2.0.0.RC >> >> I tried the corrected version of setting given: >> >> cloud: >> aws: >> access_key: XXXXXX >> secret_key: XXXXXX >> region: ap-southeast-1 >> discovery: >> type: ec2 >> groups: <security Group name> >> >> Difference is the region. >> >> I have created two nodes(one is master node with node.data = false and >> other one is just a data node with node.master = false) >> >> Even when I try for unicast and specify hard coded private ip then also >> the second node does not joins the cluster. >> >> I installed head plugin on the master node which is working fine and I m >> able to view one node in the browser. >> >> >> Please guide me on what I am doing wrong. >> >> >> >> >> >> On Thursday, March 20, 2014 3:51:36 AM UTC+5:30, Daniel F. wrote: >>> >>> Thanks David, >>> >>> You are right elasticsearch.yml had two errors: space before "discovery" >>> and "region" should not be equal to availability zone "eu-west-1a" but " >>> eu-west-1". >>> >>> The working version is: >>> >>> discovery.zen.ping.multicast.enabled: false >>> >>> cloud: >>> aws: >>> access_key: XXXX >>> secret_key: XXXX >>> region: eu-west-1 >>> discovery: >>> type: ec2 >>> groups: my-security-group >>> >>> Daniel >>> >>> On Wednesday, March 19, 2014 10:21:36 PM UTC+2, David Pilato wrote: >>>> >>>> I think your elasticsearch.yml is incorrect. >>>> >>>> Just saying because as far as I can see, ec2 discovery does not start >>>> actually. >>>> So, may be some space before cloud.type: ec2 is missing? >>>> >>>> >>>> -- >>>> *David Pilato* | *Technical Advocate* | *Elasticsearch.com >>>> <http://Elasticsearch.com>* >>>> @dadoonet <https://twitter.com/dadoonet> | >>>> @elasticsearchfr<https://twitter.com/elasticsearchfr> >>>> >>>> >>>> Le 19 mars 2014 à 19:31:03, Daniel F. (feins...@gmail.com) a écrit: >>>> >>>> Yes, i am running elasticsearch as root. It is a test environment so >>>> I did not tune it yet. >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "elasticsearch" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to elasticsearc...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/5f49602f-9db0-4e68-9037-310a87064f1e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to elasticsearch+unsubscr...@googlegroups.com. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/5d40ca9c-ea3b-4d21-84a1-3f6ef907a80e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "elasticsearch" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> elasticsearch+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr<https://groups.google.com/d/msgid/elasticsearch/E4CABFBD-9F00-4AB0-9CC7-F06D05B52C9F%40pilato.fr?utm_medium=email&utm_source=footer>. >> >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAEXePwfmAyp9K88ykHUk78C6tyFPDvr9jFXSV%2BWSoJ3_7xDe-Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/VyFXBVFp_oM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local<https://groups.google.com/d/msgid/elasticsearch/etPan.532bfcac.4353d0cd.c9bd%40MacBook-Air-de-David.local?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEXePwcVNDYoNQ%3DdA8eTtiq5J6aXLZZtioRN-DE-o8YOR2OBNg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
