Hello,
I'm evaluating search engines and elasticsearch in particular to setup
distributed search in AWS. What I found is that cloud-aws supports single
region and multiple availability zones for clustering. I'm wondering is
this possible to support multiple regions as well? That way I can split
elasticsearch servers across us-east-1, us-west-1 and eu-west-1 and provide
reasonably small response time for users in US and Europe with a single
cluster.
Thanks.
bump
On Thursday, 14 June 2012 13:49:49 UTC+1, Eduard Dudar wrote:
Hello,
I'm evaluating search engines and elasticsearch in particular to setup
distributed search in AWS. What I found is that cloud-aws supports single
region and multiple availability zones for clustering. I'm wondering is
this possible to support multiple regions as well? That way I can split
elasticsearch servers across us-east-1, us-west-1 and eu-west-1 and provide
reasonably small response time for users in US and Europe with a single
cluster.
Thanks.
--
Found a solution - simply setup one cluster on eu-west (or wherever else),
then on servers in different region give:
cloud.aws.region: eu-west
Autodiscovery will search for servers in eu-west in this case [ and it
works for me ]
On Thursday, 14 June 2012 13:49:49 UTC+1, Eduard Dudar wrote:
Hello,
I'm evaluating search engines and elasticsearch in particular to setup
distributed search in AWS. What I found is that cloud-aws supports single
region and multiple availability zones for clustering. I'm wondering is
this possible to support multiple regions as well? That way I can split
elasticsearch servers across us-east-1, us-west-1 and eu-west-1 and provide
reasonably small response time for users in US and Europe with a single
cluster.
Thanks.
--
Hi Lukasz,
I'm having trouble setting up multi region support with instances in US &
EU. ES seems to be finding the other machine but looking it up using
internal 10.* IP address. Did you have to configure fixed external IP's or
change your local /hosts/ settings to allow communication over the seperate
regions?
Derry
On Thursday, 23 August 2012 16:39:02 UTC+1, Lukasz Raczylo wrote:
Found a solution - simply setup one cluster on eu-west (or wherever else),
then on servers in different region give:
cloud.aws.region: eu-west
Autodiscovery will search for servers in eu-west in this case [ and it
works for me ]
On Thursday, 14 June 2012 13:49:49 UTC+1, Eduard Dudar wrote:
Hello,
I'm evaluating search engines and elasticsearch in particular to setup
distributed search in AWS. What I found is that cloud-aws supports single
region and multiple availability zones for clustering. I'm wondering is
this possible to support multiple regions as well? That way I can split
elasticsearch servers across us-east-1, us-west-1 and eu-west-1 and provide
reasonably small response time for users in US and Europe with a single
cluster.
Thanks.
--
http://www.raczylo.com/blog/Elasticsearch-AWS-and-different-availability-zones.html
Step-by-step instructions I've hope that you'll find it useful
On Friday, 28 September 2012 08:32:06 UTC+1, Derry O' Sullivan wrote:
Hi Lukasz,
I'm having trouble setting up multi region support with instances in US &
EU. ES seems to be finding the other machine but looking it up using
internal 10.* IP address. Did you have to configure fixed external IP's or
change your local /hosts/ settings to allow communication over the seperate
regions?
Derry
On Thursday, 23 August 2012 16:39:02 UTC+1, Lukasz Raczylo wrote:
Found a solution - simply setup one cluster on eu-west (or wherever
else), then on servers in different region give:
cloud.aws.region: eu-west
Autodiscovery will search for servers in eu-west in this case [ and it
works for me ]
On Thursday, 14 June 2012 13:49:49 UTC+1, Eduard Dudar wrote:
Hello,
I'm evaluating search engines and elasticsearch in particular to setup
distributed search in AWS. What I found is that cloud-aws supports single
region and multiple availability zones for clustering. I'm wondering is
this possible to support multiple regions as well? That way I can split
elasticsearch servers across us-east-1, us-west-1 and eu-west-1 and provide
reasonably small response time for users in US and Europe with a single
cluster.
Thanks.
--