# Cluster allocation awareness - opposite
**URL:** https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755
**Category:** Elasticsearch
**Created:** [September 12, 2014, 12:40pm UTC](https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755 "2014-09-12T12:40:12Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@spezam](https://discuss.elastic.co/u/spezam)
#### Post date: [September 12, 2014, 12:40pm UTC](https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755/1 "2014-09-12T12:40:12Z")
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?
Thanks a million,
Matteo
--
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 12, 2014, 10:40pm UTC](https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755/2 "2014-09-12T22:40:24Z")
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?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
On 12 September 2014 22:40, spezam [spezam@gmail.com](mailto:spezam@gmail.com) 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?
>
> Thanks a million,
> Matteo
>
> --
> 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com)
> [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com?utm_medium=email&utm_source=footer)
> .
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624Y-3rjNgomPDz24mCKRb0c5Fo6Hd8KKwRaoo8M%2BL%2BWPsQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624Y-3rjNgomPDz24mCKRb0c5Fo6Hd8KKwRaoo8M%2BL%2BWPsQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@spezam](https://discuss.elastic.co/u/spezam)
#### Post date: [September 15, 2014, 8:03am UTC](https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755/3 "2014-09-15T08:03:41Z")
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?
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
>
> On 12 September 2014 22:40, spezam \<[spe...@gmail.com](mailto:spe...@gmail.com) \\> 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?
> >
> > Thanks a million,
> > Matteo
> >
> > --
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \.
> > To view this discussion on the web visit
> > [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com)
> > [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com?utm_medium=email&utm_source=footer)
> > .
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4100dab3-e194-4834-94cb-6601d98194d0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4100dab3-e194-4834-94cb-6601d98194d0%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@spezam](https://discuss.elastic.co/u/spezam)
#### Post date: [September 21, 2014, 9:26am UTC](https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755/4 "2014-09-21T09:26:30Z")
At the end, I decided to divide the single cluster in clusterS and use the
new tribe capabilities.
> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.
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?
> >
> > Regards,
> > Mark Walkom
> >
> > Infrastructure Engineer
> > Campaign Monitor
> > email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com)
> > web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> >
> > On 12 September 2014 22:40, spezam [spe...@gmail.com](mailto:spe...@gmail.com) 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?
> > >
> > > Thanks a million,
> > > Matteo
> > >
> > > --
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > > To view this discussion on the web visit
> > > [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com)
> > > [https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/3cff8e6e-9b3b-432c-baba-03dd44b3862c%40googlegroups.com?utm_medium=email&utm_source=footer)
> > > .
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/58116aca-41b8-4f43-9ad9-09f0ef67b072%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/58116aca-41b8-4f43-9ad9-09f0ef67b072%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:00am UTC](https://discuss.elastic.co/t/cluster-allocation-awareness-opposite/19755/5 "2017-07-06T01:00:56Z")