# Tier Preference is not using the secondary option for replica **URL:** https://discuss.elastic.co/t/tier-preference-is-not-using-the-secondary-option-for-replica/364008 **Category:** Elasticsearch **Created:** [July 29, 2024, 8:29pm UTC](https://discuss.elastic.co/t/tier-preference-is-not-using-the-secondary-option-for-replica/364008 "2024-07-29T20:29:58Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![jsheely](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsheely/32/135689_2.png) [@jsheely](https://discuss.elastic.co/u/jsheely) #### Post date: [July 29, 2024, 10:32pm UTC](https://discuss.elastic.co/t/tier-preference-is-not-using-the-secondary-option-for-replica/364008/2 "2024-07-29T22:32:58Z")
I found an older reference post that describes my problem exactly in more detail. However the described fix does not make sense to me. > [@Shard allocation - strange behaviour of index tier preference](https://discuss.elastic.co/t/shard-allocation-strange-behaviour-of-index-tier-preference/326746/9): > > Can't get it to work. I created a brand new 2h/2w cluster. # Creating the index PUT test1 { "settings": { "index.routing.allocation.include.\_tier\_preference": null, "number\_of\_replicas": 2 } } # GET \_cat/shards/test1?v 200 OK index shard prirep state docs store ip node test1 0 p STARTED 0 225b 10.47.192.173 instance-0000000000 test1 0 r STARTED 0 225b 10.47.192.99 instance-0000000001 test1 0 r UNASSIGNED … Setting \_tier\_preference to null seems to ignore desired result of having the settings to decide which tier I want the node to be on. --- _[View the full topic](https://discuss.elastic.co/t/tier-preference-is-not-using-the-secondary-option-for-replica/364008)._