[
https://issues.apache.org/jira/browse/WHIRR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010245#comment-13010245
]
Andrei Savu commented on WHIRR-261:
-----------------------------------
By default Whirr will configure elasticsearch to use the EC2 discovery module
on AWS and store the index in memory with no disk data persistence. On
cloudservers I'm thinking about using unicast and build a list of hosts. All
configuration parameters can be set in the cluster spec .properties file. A
typical recipe for AWS looks like this:
{code}
# Change the cluster name here
whirr.cluster-name=elasticsearch
# This is also the elasticsearch cluster name
# Change the number of machines in the cluster here
whirr.instance-templates=2 elasticsearch
whirr.hardware-min-ram=2048
# For EC2 set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
# S3 persistence
es.gateway.type=s3
es.gateway.s3.bucket=elasticsearch
{code}
> Add ElasticSearch as a service
> ------------------------------
>
> Key: WHIRR-261
> URL: https://issues.apache.org/jira/browse/WHIRR-261
> Project: Whirr
> Issue Type: New Feature
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.5.0
>
> Attachments: WHIRR-261.patch, WHIRR-261.patch, WHIRR-261.patch
>
>
> ElasticSearch is a distributed RESTful search engine built for the cloud.
> [1] http://www.elasticsearch.org/
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
