Re: Elasticsearch 1.0.1 on AWS

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: XX secret_key: XX region: ap-southeast-1 discovery: type: ec2

Re: Elasticsearch 1.0.1 on AWS

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

Re: Elasticsearch 1.0.1 on AWS

/ @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

Re: Elasticsearch 1.0.1 on AWS

for ec2 discovery. Regards Geet On Fri, Mar 21, 2014 at 2:46 PM, Geet Gangwar geetgang...@gmail.com wrote: 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

Re: Bulk throughput issues

Thanks tdjb, I followed your code and it worked for me, I tried to set the refresh_interval in the transport client setting but it seems its not working. Please suggest me how can set the refresh interval using transport client. Regards Geet On Fri, Jan 3, 2014 at 8:32 PM, tdjb