# Attribute awareness during recovery? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 24, 2015, 10:18am UTC](https://discuss.elastic.co/t/attribute-awareness-during-recovery/22349 "2015-02-24T10:18:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![andrassy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrassy/32/32783_2.png) [@andrassy](https://discuss.elastic.co/u/andrassy)\ **Post date:** [February 24, 2015, 10:18am UTC](https://discuss.elastic.co/t/attribute-awareness-during-recovery/22349/1 "2015-02-24T10:18:02Z")
Hi, Does anybody know if there is a way, when a node fails and shards need to be recovered, of configuring ElasticSearch to prefer to recover from a node sharing the same awareness attributes (e.g. same rack, same zone etc. a bit like the "automatic preference when searching / getingedit" reference in the user guide). We're typically seeing a lot of traffic between "zones" when a failure occurs and I wondered why this was the case / if it was avoidable. Maybe I'm missing something and recovery always needs to replicate from the active primary? Thanks in advance for any guidance or information, N -- 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/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 25, 2015, 6:56am UTC](https://discuss.elastic.co/t/attribute-awareness-during-recovery/22349/2 "2015-02-25T06:56:04Z")
Recovery always needs to come from the primary, otherwise you cannot be certain your dataset is valid. On 24 February 2015 at 21:18, Neil Andrassy [neil.andrassy@thefilter.com](mailto:neil.andrassy@thefilter.com) wrote: > Hi, > > Does anybody know if there is a way, when a node fails and shards need to > be recovered, of configuring Elasticsearch to prefer to recover from a node > sharing the same awareness attributes (e.g. same rack, same zone etc. a bit > like the "automatic preference when searching / getingedit" reference in > the user guide). We're typically seeing a lot of traffic between "zones" > when a failure occurs and I wondered why this was the case / if it was > avoidable. Maybe I'm missing something and recovery always needs to > replicate from the active primary? > > Thanks in advance for any guidance or information, > > N > > -- > 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/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%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/CAEYi1X\_ihD\_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ihD_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![andrassy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrassy/32/32783_2.png) [@andrassy](https://discuss.elastic.co/u/andrassy)\ **Post date:** [February 25, 2015, 12:35pm UTC](https://discuss.elastic.co/t/attribute-awareness-during-recovery/22349/3 "2015-02-25T12:35:39Z")
That seems like a shame given the immutability of the underlying blocks. Sure, the primary needs to identify the specific set of blocks to be replicated but I don't see why the block data itself couldn't be pulled from a "closer" replica if it exists there? On 25 February 2015 at 06:56, Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com) wrote: > Recovery always needs to come from the primary, otherwise you cannot be > certain your dataset is valid. > > On 24 February 2015 at 21:18, Neil Andrassy [neil.andrassy@thefilter.com](mailto:neil.andrassy@thefilter.com) > wrote: > > > Hi, > > > > Does anybody know if there is a way, when a node fails and shards need to > > be recovered, of configuring Elasticsearch to prefer to recover from a node > > sharing the same awareness attributes (e.g. same rack, same zone etc. a bit > > like the "automatic preference when searching / getingedit" reference in > > the user guide). We're typically seeing a lot of traffic between "zones" > > when a failure occurs and I wondered why this was the case / if it was > > avoidable. Maybe I'm missing something and recovery always needs to > > replicate from the active primary? > > > > Thanks in advance for any guidance or information, > > > > N > > > > -- > > 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/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%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 a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/txa\_4eosq0k/unsubscribe](https://groups.google.com/d/topic/elasticsearch/txa_4eosq0k/unsubscribe). > To unsubscribe from this group and all its topics, 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/CAEYi1X\_ihD\_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ihD_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X\_ihD\_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ihD_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Neil Andrassy | CTO | The Filter phone | +44 (0)1225 588 004 skype | andrassynp -- 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/CABpTWLObLq3tJuE48p0OfdwoXB6KoAHZvKbi6x%2B98SjuPfrP7A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CABpTWLObLq3tJuE48p0OfdwoXB6KoAHZvKbi6x%2B98SjuPfrP7A%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 25, 2015, 9:55pm UTC](https://discuss.elastic.co/t/attribute-awareness-during-recovery/22349/4 "2015-02-25T21:55:06Z")
Define closer though, someone might use zone awareness on a rack or room level, these are just abstracted concepts/tags after all. On 25 February 2015 at 23:35, Neil Andrassy (The Filter) \< [neil.andrassy@thefilter.com](mailto:neil.andrassy@thefilter.com)\> wrote: > That seems like a shame given the immutability of the underlying blocks. > Sure, the primary needs to identify the specific set of blocks to be > replicated but I don't see why the block data itself couldn't be pulled > from a "closer" replica if it exists there? > > On 25 February 2015 at 06:56, Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com) wrote: > > > Recovery always needs to come from the primary, otherwise you cannot be > > certain your dataset is valid. > > > > On 24 February 2015 at 21:18, Neil Andrassy [neil.andrassy@thefilter.com](mailto:neil.andrassy@thefilter.com) > > wrote: > > > > > Hi, > > > > > > Does anybody know if there is a way, when a node fails and shards need > > > to be recovered, of configuring Elasticsearch to prefer to recover from a > > > node sharing the same awareness attributes (e.g. same rack, same zone etc. > > > a bit like the "automatic preference when searching / getingedit" reference > > > in the user guide). We're typically seeing a lot of traffic between "zones" > > > when a failure occurs and I wondered why this was the case / if it was > > > avoidable. Maybe I'm missing something and recovery always needs to > > > replicate from the active primary? > > > > > > Thanks in advance for any guidance or information, > > > > > > N > > > > > > -- > > > 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/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/dfa05e57-15a8-4509-a45f-62db4d94867a%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 a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/txa\_4eosq0k/unsubscribe](https://groups.google.com/d/topic/elasticsearch/txa_4eosq0k/unsubscribe). > > To unsubscribe from this group and all its topics, 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/CAEYi1X\_ihD\_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ihD_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com) > > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X\_ihD\_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ihD_AkLgoF5FjAJbju9dnCAwAYhoZbns-gf%2BWYXWQMQ%40mail.gmail.com?utm_medium=email&utm_source=footer) > > . > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > Neil Andrassy | CTO | The Filter > phone | +44 (0)1225 588 004 > skype | andrassynp > > -- > 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/CABpTWLObLq3tJuE48p0OfdwoXB6KoAHZvKbi6x%2B98SjuPfrP7A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CABpTWLObLq3tJuE48p0OfdwoXB6KoAHZvKbi6x%2B98SjuPfrP7A%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CABpTWLObLq3tJuE48p0OfdwoXB6KoAHZvKbi6x%2B98SjuPfrP7A%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CABpTWLObLq3tJuE48p0OfdwoXB6KoAHZvKbi6x%2B98SjuPfrP7A%40mail.gmail.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/CAEYi1X\_ymUMvG0VXH29\_q-\_LN0fM0cV1hgxpvVSZEAS10XAg1Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ymUMvG0VXH29_q-_LN0fM0cV1hgxpvVSZEAS10XAg1Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:30am UTC](https://discuss.elastic.co/t/attribute-awareness-during-recovery/22349/5 "2017-07-06T00:30:03Z")
Closed on July 6, 2017, 12:30am UTC