Thanks David, This is the plugin version I use. In plugins/cloud-aws/ I have elasticsearch-cloud-aws-2.0.0.RC1.jar.
The log level is set to TRACE in logging.yml: # discovery discovery: TRACE elasticsearch.yml settings: discovery.zen.ping.multicast.enabled: false cloud: aws: access_key: XXXX secret_key: XXXX region: eu-west-1a discovery: type: ec2 groups: my-security-group The log for all discovery records is: [2014-03-19 15:45:12,398][DEBUG][discovery.zen.ping.unicast] [Annie Ghazikhanian] using initial hosts [], with concurrent_connects [10] [2014-03-19 15:45:12,399][DEBUG][discovery.zen ] [Annie Ghazikhanian] using ping.timeout [3s], master_election.filter_client [true], master_election.filter_data [false] [2014-03-19 15:45:12,400][DEBUG][discovery.zen.elect ] [Annie Ghazikhanian] using minimum_master_nodes [1] [2014-03-19 15:45:12,401][DEBUG][discovery.zen.fd ] [Annie Ghazikhanian] [master] uses ping_interval [1s], ping_timeout [30s], ping_retries [3] [2014-03-19 15:45:12,420][DEBUG][discovery.zen.fd ] [Annie Ghazikhanian] [node ] uses ping_interval [1s], ping_timeout [30s], ping_retries [3] [2014-03-19 15:45:14,186][TRACE][discovery ] [Annie Ghazikhanian] waiting for 30s for the initial state to be set by the discovery [2014-03-19 15:45:17,191][TRACE][discovery.zen ] [Annie Ghazikhanian] full ping responses: {none} [2014-03-19 15:45:17,191][DEBUG][discovery.zen ] [Annie Ghazikhanian] filtered ping responses: (filter_client[true], filter_data[false]) {none} [2014-03-19 15:45:17,223][TRACE][discovery ] [Annie Ghazikhanian] initial state set from discovery [2014-03-19 15:45:17,266][INFO ][discovery ] [Annie Ghazikhanian] toluna-es-test-cluster-eu/1UlTwLC9TsOfg_Mky1G3Cw As you could see there are no ec2 discovery records in the log. What do I miss? On Wednesday, March 19, 2014 5:20:27 PM UTC+2, David Pilato wrote: > > cloud-aws 2.0.0.RC1 is supposed to work with es 1.0.1. > A new version will come really soon when we will have merged a pending PR. > > If you want to make sure that everything is running correctly, you could > change logging.yml file and set discovery to TRACE > > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | > @elasticsearchfr<https://twitter.com/elasticsearchfr> > > > Le 19 mars 2014 à 16:12:27, Daniel F. (feins...@gmail.com <javascript:>) > a écrit: > > Hi, > > I am testing Elasticsearch version 1.0.1 on AWS. I have followed > documentation of Elasticsearch ( > http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/) and > installed latest EC2 plugin. In the log I have seen that the system have > recognized the installed plugin but no ec2 discovery logs appeared. For a > while I am using unicast discovery but it is really not convenient. > > Does somebody know if there is a known problem in the plugin? Does the > plugin work with 1.0.1 version of Elasticsearch? Any other suggestions are > welcome. > > Thanks, > -- > 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 <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/f84410f5-ec3e-4fb8-854e-ff45aefe7ad9%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/d28f7292-b0ff-4207-8a35-15fba7a595b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.