# Warm tier shards being allocated to data nodes
**URL:** https://discuss.elastic.co/t/warm-tier-shards-being-allocated-to-data-nodes/334136
**Category:** Elasticsearch
**Created:** [May 23, 2023, 2:49pm UTC](https://discuss.elastic.co/t/warm-tier-shards-being-allocated-to-data-nodes/334136 "2023-05-23T14:49:15Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Mirko\_Katunar](https://discuss.elastic.co/u/Mirko_Katunar)
#### Post date: [May 23, 2023, 2:49pm UTC](https://discuss.elastic.co/t/warm-tier-shards-being-allocated-to-data-nodes/334136/1 "2023-05-23T14:49:15Z")
Hello,
I have a hot, warm architecture and 3 master nodes that are also data nodes. At some point Elastic started to allocate data stream shards that are in warm tier to master/data nodes. As plain data node can fill any of the specialized data node roles I assume it just views data nodes as warm tier nodes as well and completely ignores dynamic configuration in elasticsearch.yml file.
Any idea how to more specifically set master/data nodes only to hold system indices/shards and not data stream ones that should be on dedicated data\_hot and data\_warm nodes.
Thank you
---
### Author:  [@Mirko\_Katunar](https://discuss.elastic.co/u/Mirko_Katunar)
#### Post date: [May 24, 2023, 8:18am UTC](https://discuss.elastic.co/t/warm-tier-shards-being-allocated-to-data-nodes/334136/2 "2023-05-24T08:18:29Z")
Switching them to master/data\_content role solved this allocation issue.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 21, 2023, 8:19am UTC](https://discuss.elastic.co/t/warm-tier-shards-being-allocated-to-data-nodes/334136/3 "2023-06-21T08:19:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.