Sorry for confusion I have tried to post only relevant information here. There are many lines between
discovery.zen.ping.multicast.enabled: false and ec2 discovery configurations. In the folder plugins/cloud-aws/ I have the following files: -rw-r--r-- 1 root root 9276981 Mar 9 11:53 aws-java-sdk-1.3.32.jar -rw-r--r-- 1 root root 58160 Mar 9 11:53 commons-codec-1.4.jar -rw-r--r-- 1 root root 60686 Mar 9 11:53 commons-logging-1.1.1.jar -rw-r--r-- 1 root root 45197 Mar 9 11:53 elasticsearch-cloud-aws-2.0.0.RC1.jar -rw-r--r-- 1 root root 351132 Mar 9 11:53 httpclient-4.1.1.jar -rw-r--r-- 1 root root 181041 Mar 9 11:53 httpcore-4.1.jar On Wednesday, March 19, 2014 5:12:23 PM UTC+2, Daniel F. wrote: > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fde9d055-a854-412c-8f76-5c7bafc07cd9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
