# Zone awareness-alike behaviour for single index **URL:** \ **Category:** Elasticsearch\ **Created:** [October 13, 2016, 9:01pm UTC](https://discuss.elastic.co/t/zone-awareness-alike-behaviour-for-single-index/63000 "2016-10-13T21:01:20Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![shog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shog/32/12138_2.png) [@shog](https://discuss.elastic.co/u/shog)\ **Post date:** [October 13, 2016, 9:01pm UTC](https://discuss.elastic.co/t/zone-awareness-alike-behaviour-for-single-index/63000/1 "2016-10-13T21:01:20Z")
Hi, It would be cool if something like zone awareness behaviour would be easily achieved on per-index level. Example use case here is: some older/cold indexes, that I'd like to offload to storage nodes, but still keep replica of data on faster nodes too. Unfortunately include/require/exclude allocation filters aren't really capable to achieve that (as I can only move index with all its shards). Or maybe I'm missing something and this is possible? ---
**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:** [October 14, 2016, 8:01am UTC](https://discuss.elastic.co/t/zone-awareness-alike-behaviour-for-single-index/63000/2 "2016-10-14T08:01:11Z")
It's not possible. And it doesn't make a lot of sense. Actions against an index set (primary + replica/s) is done synchronously. So If you had the replicas on slow hardware it'd impact overall performance. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:12pm UTC](https://discuss.elastic.co/t/zone-awareness-alike-behaviour-for-single-index/63000/3 "2017-07-05T22:12:25Z")
Closed on July 5, 2017, 10:12pm UTC