Hi, Ok........problem solved....was not discovery., I was the attachment of the volume. This brings up another issue.....why did I not get an error?
logger: # log action execution errors for easier debugging action: DEBUG I just removed this line form elasticsearch.yml: path.data: /data I attachment is formated as mkfs.ext3 and the volume exists. is not path.data: /data is method to specify where the data should be stored? Thanks On Monday, January 27, 2014 12:32:01 AM UTC+8, Karel Minařík wrote: > > > 4) I did not have a problem with ES when not using aws for auto > discovery. Is there another way to cluster machines on aws? Clearly there > is an issues somewhere. If I have 2 or more machines..is there another > way? > > The AWS discovery mechanism is alive and kicking in most cases. Based on > your description, you seem to not be able to *start* Elasticsearch with the > plugin installed. Is that the case? > > For the AWS discovery to work, you have to open port 9300-9400 among the > Elasticsearch instances. Have you done so? > > Best way how to achieve that in EC2 is to have a dedicated security group, > which opens these ports to "itself". Screenshot (of the old AWS console): > http://www.elasticsearch.org/content/themes/elasticsearch-org/images/content/chef-solo/create-security-group.png > > > Karel > > -- 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/e636e0fd-406e-4286-8633-cf8db252be0c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
