Hi All,
we currently have an Elasticsearch (1.1.1) cluster distributed among DCs
3 Data nodes in 3 DC
1 Gateway node
each DC index its own data and no shards replica is happening between DC.
The gateway lets us to query all the indexes in all the DC.
Now, for performance and redundancy we would like to add one data node per
DC and replicate the 'local' indexes.
We read about cluster allocation awareness, and thought that was the
perfect solution, until we realize it actually acts opposite of what we
want.
If node members are in the same awareness attribute, they would just
'ignore' each others and don't spread shards or replicate.
Is such a deployment possible/does it makes sense?
You indicate you have a single cluster but then no replication happens
between the nodes in each DC?
By gateway do you mean a tribe node?
And by replicate the local indexes do you want to set replicas = 1 and then
have them on this new node in each DC?
Hi All,
we currently have an Elasticsearch (1.1.1) cluster distributed among DCs
3 Data nodes in 3 DC
1 Gateway node
each DC index its own data and no shards replica is happening between DC.
The gateway lets us to query all the indexes in all the DC.
Now, for performance and redundancy we would like to add one data node per
DC and replicate the 'local' indexes.
We read about cluster allocation awareness, and thought that was the
perfect solution, until we realize it actually acts opposite of what we
want.
If node members are in the same awareness attribute, they would just
'ignore' each others and don't spread shards or replicate.
Is such a deployment possible/does it makes sense?
Hi Mark,
precise, there's no replication happening between the nodes in the DC, they
are just aware of each others.
The gateway is a no-data node that is used by Kibana to query all the other
nodes in the cluster and return aggregated queries.
Yes, I would like to add a new node (node2) in DC1 (for example) and
replicate data between node1 and node2 in the same DC.
On Saturday, September 13, 2014 12:40:51 AM UTC+2, Mark Walkom wrote:
It's a little unclear what you are doing.
You indicate you have a single cluster but then no replication happens
between the nodes in each DC?
By gateway do you mean a tribe node?
And by replicate the local indexes do you want to set replicas = 1 and
then have them on this new node in each DC?
On 12 September 2014 22:40, spezam <spe...@gmail.com <javascript:>> wrote:
Hi All,
we currently have an Elasticsearch (1.1.1) cluster distributed among DCs
3 Data nodes in 3 DC
1 Gateway node
each DC index its own data and no shards replica is happening between DC.
The gateway lets us to query all the indexes in all the DC.
Now, for performance and redundancy we would like to add one data node
per DC and replicate the 'local' indexes.
We read about cluster allocation awareness, and thought that was the
perfect solution, until we realize it actually acts opposite of what we
want.
If node members are in the same awareness attribute, they would just
'ignore' each others and don't spread shards or replicate.
Is such a deployment possible/does it makes sense?
At the end, I decided to divide the single cluster in clusterS and use the
new tribe capabilities.
it works really good.
On Monday, September 15, 2014 10:03:41 AM UTC+2, spezam wrote:
Hi Mark,
precise, there's no replication happening between the nodes in the DC,
they are just aware of each others.
The gateway is a no-data node that is used by Kibana to query all the
other nodes in the cluster and return aggregated queries.
Yes, I would like to add a new node (node2) in DC1 (for example) and
replicate data between node1 and node2 in the same DC.
On Saturday, September 13, 2014 12:40:51 AM UTC+2, Mark Walkom wrote:
It's a little unclear what you are doing.
You indicate you have a single cluster but then no replication happens
between the nodes in each DC?
By gateway do you mean a tribe node?
And by replicate the local indexes do you want to set replicas = 1 and
then have them on this new node in each DC?
Hi All,
we currently have an Elasticsearch (1.1.1) cluster distributed among DCs
3 Data nodes in 3 DC
1 Gateway node
each DC index its own data and no shards replica is happening between DC.
The gateway lets us to query all the indexes in all the DC.
Now, for performance and redundancy we would like to add one data node
per DC and replicate the 'local' indexes.
We read about cluster allocation awareness, and thought that was the
perfect solution, until we realize it actually acts opposite of what we
want.
If node members are in the same awareness attribute, they would just
'ignore' each others and don't spread shards or replicate.
Is such a deployment possible/does it makes sense?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.