# Unassigned shards with new frozen tier **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [May 27, 2021, 9:32pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265 "2021-05-27T21:32:34Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\ **Post date:** [May 27, 2021, 9:32pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265/1 "2021-05-27T21:32:34Z")
I have spun up a brand new cluster on elastic cloud to test 7.13 and I have data\_hot and data\_frozen tiers. I've changed ILM policy for logs and metrics so that data that is older than a few hours (just to test) is moved to frozen tier however (and this is the third cluster I have tried this on) after the indexes move to frozen tier the cluster goes to red state with unassigned shards? ---
**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:** [May 27, 2021, 11:10pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265/2 "2021-05-27T23:10:17Z")
What's your policy? Can you run an explain on it? What about the output from `GET _cluster/allocation/explain?` ---
**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\ **Post date:** [May 27, 2021, 11:15pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265/3 "2021-05-27T23:15:22Z")
> [@warkolm](#): > > `GET _cluster/allocation/explain?` Hmmm doesn't look like the data\_hot node is actually assigned the role? ```auto { "can_allocate": "no", "index": ".ds-metrics-system.process-default-2021.05.27-000004", "node_allocation_decisions": [ { "node_decision": "no", "transport_address": "10.46.88.21:19990", "weight_ranking": 1, "node_name": "instance-0000000003", "node_id": "VXPR1rrYSduESDNtN5pq3Q", "deciders": [ { "decision": "NO", "explanation": "the node is above the low watermark cluster setting [cluster.routing.allocation.disk.watermark.low=85%], using more disk space than the maximum allowed [85.0%], actual free: [9.991089502970379%]", "decider": "disk_threshold" }, { "decision": "NO", "explanation": "index has a preference for tiers [data_hot] and node does not meet the required [data_hot] tier", "decider": "data_tier" }, { "decision": "NO", "explanation": "this node's data roles are exactly [data_frozen] so it may only hold shards from frozen searchable snapshots, but this index is not a frozen searchable snapshot", "decider": "dedicated_frozen_node" } ], "node_attributes": { "server_name": "instance-0000000003.74708265f72e4930aa084f14d02f51c3", "availability_zone": "westus2-2", "transform.node": "false", "region": "unknown-region", "instance_configuration": "azure.es.datafrozen.lsv2", "xpack.installed": "true", "logical_availability_zone": "zone-0", "data": "frozen" } }, { "node_decision": "no", "transport_address": "10.46.88.114:19646", "weight_ranking": 2, "node_name": "instance-0000000000", "node_id": "lny_G1ToTQC20sYpdheryw", "deciders": [ { "decision": "NO", "explanation": "a copy of this shard is already allocated to this node [[.ds-metrics-system.process-default-2021.05.27-000004][0], node[lny_G1ToTQC20sYpdheryw], [P], s[STARTED], a[id=Z_9a9u8gS-WC8zXuInRwNw]]", "decider": "same_shard" } ], "node_attributes": { "server_name": "instance-0000000000.74708265f72e4930aa084f14d02f51c3", "availability_zone": "westus2-3", "transform.node": "true", "region": "unknown-region", "instance_configuration": "azure.data.highio.l32sv2", "xpack.installed": "true", "logical_availability_zone": "zone-0", "data": "hot" } } ], "current_state": "unassigned", "shard": 0, "primary": false, "allocate_explanation": "cannot allocate because allocation is not permitted to any of the nodes", "unassigned_info": { "last_allocation_status": "no_attempt", "reason": "INDEX_CREATED", "at": "2021-05-27T22:11:31.868Z" } } ``` My ILM policy ```auto PUT _ilm/policy/logs { "policy": { "phases": { "hot": { "min_age": "0ms", "actions": { "shrink": { "number_of_shards": 1 }, "rollover": { "max_primary_shard_size": "3gb", "max_age": "3h" } } }, "frozen": { "min_age": "1h", "actions": { "searchable_snapshot": { "snapshot_repository": "found-snapshots", "force_merge_index": true } } } } } } ``` ---
**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:** [May 27, 2021, 11:27pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265/4 "2021-05-27T23:27:23Z")
> [@hilt86](#): > > ```auto > "explanation": "the node is above the low watermark cluster setting [cluster.routing.allocation.disk.watermark.low=85%], using more disk space than the maximum allowed [85.0%], actual free: [9.991089502970379%]", > > ``` Check that as well. ---
**Author:** ![hilt86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilt86/32/20308_2.png) [@hilt86](https://discuss.elastic.co/u/hilt86)\ **Post date:** [May 27, 2021, 11:37pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265/5 "2021-05-27T23:37:45Z")
It is a brand new cluster with barely 1GB data : ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/f/efb832feaec454d97fa1cf02d08cc9cbfe3435c4.png) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 24, 2021, 11:38pm UTC](https://discuss.elastic.co/t/unassigned-shards-with-new-frozen-tier/274265/6 "2021-06-24T23:38:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.