# Hot & Warm Node Allocation Replica Failure

**URL:** <https://discuss.elastic.co/t/hot-warm-node-allocation-replica-failure/80423>\
**Category:** Elasticsearch\
**Created:** [March 29, 2017, 7:33am UTC](https://discuss.elastic.co/t/hot-warm-node-allocation-replica-failure/80423 "2017-03-29T07:33:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gromit6891](https://avatars.discourse-cdn.com/v4/letter/g/53a042/32.png) [@gromit6891](https://discuss.elastic.co/u/gromit6891)\
**Post date:** [March 29, 2017, 7:33am UTC](https://discuss.elastic.co/t/hot-warm-node-allocation-replica-failure/80423/1 "2017-03-29T07:33:35Z")

</div>

Elasticsearch 2.4.3

I have six data nodes, three marked as hot and three as warm. The cluster is setup to have 1 replica. By default incoming data is distributed correctly between the six nodes with replicas. If I apply the following global template to allocate to hot nodes only, then only the primary shards are allocated to the hot nodes and the replica shards remain unassigned.

PUT /\_template/global\_settings\_allocation  
{  
"order": -1,  
"template": "\*",  
"settings": {  
"index": {  
"routing": {  
"allocation": {  
"require": {  
"box\_type": "hot"  
}  
}

```
  }
}

```

},  
"mappings": {},  
"aliases": {}  
}

Is there something more to be done here?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 26, 2017, 7:33am UTC](https://discuss.elastic.co/t/hot-warm-node-allocation-replica-failure/80423/2 "2017-04-26T07:33:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.