# Unfreeze, Read-Only, Move to Cold/Frozen

**URL:** <https://discuss.elastic.co/t/unfreeze-read-only-move-to-cold-frozen/322395>\
**Category:** Elasticsearch\
**Created:** [January 3, 2023, 3:37pm UTC](https://discuss.elastic.co/t/unfreeze-read-only-move-to-cold-frozen/322395 "2023-01-03T15:37:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\
**Post date:** [January 3, 2023, 3:37pm UTC](https://discuss.elastic.co/t/unfreeze-read-only-move-to-cold-frozen/322395/1 "2023-01-03T15:37:04Z")

</div>

Team,

I'm working through the Elastic Upgrade Assistant and its telling me I have 38 Warnings, all the same warning, that I need to, **"Index [XYZ] is frozen. Frozen indices no longer offer any advantages. Instead, unfreeze the index, make it read-only, and move it to the cold or frozen tier."** What are the steps that I need to take here?

```nohighlight
1. POST /<index>/_unfreeze
2. PUT your_index/_settings
{
  "index": {
    "blocks.read_only": true
  }
}
3. Set to cold tier?

```

Thank you.

---

<div class="post-metadata">

**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:** [January 4, 2023, 12:25am UTC](https://discuss.elastic.co/t/unfreeze-read-only-move-to-cold-frozen/322395/2 "2023-01-04T00:25:21Z")

</div>

That's all correct, moving it to the cold tier would be a [reallocation](https://www.elastic.co/guide/en/elasticsearch/reference/8.5/shard-allocation-filtering.html) request based on your node tiering.

---

<div class="post-metadata">

**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\
**Post date:** [January 4, 2023, 6:40pm UTC](https://discuss.elastic.co/t/unfreeze-read-only-move-to-cold-frozen/322395/3 "2023-01-04T18:40:33Z")

</div>

Mark,

Completed steps would look like this then:

1. POST /\<your\_index\>/\_unfreeze
2. PUT \<your\_index\>/\_settings  
{  
"index": {  
"blocks.read\_only": true  
}  
}
3. PUT \<your\_index\>/\_settings  
{  
"index.routing.allocation.require.\_tier": "data\_cold" // or your specific tier name  
}

Ryan

---

<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:** [February 1, 2023, 6:40pm UTC](https://discuss.elastic.co/t/unfreeze-read-only-move-to-cold-frozen/322395/4 "2023-02-01T18:40:35Z")

</div>

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