# Index blocks write operation when it moved to warm phase by ILM
**URL:** https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552
**Category:** Elasticsearch
**Created:** [August 9, 2019, 6:57am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552 "2019-08-09T06:57:47Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@worapojc](https://discuss.elastic.co/u/worapojc)
#### Post date: [August 9, 2019, 6:57am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/1 "2019-08-09T06:57:47Z")
Hi Elasticsearch team,
Index blocks write operation when it moved to the warm phase by ILM.
```
{
"indices" : {
"nxlog-2019.08.06" : {
"index" : "nxlog-2019.08.06",
"managed" : true,
"policy" : "compass-clients-policy",
"lifecycle_date_millis" : 1564987134180,
"phase" : "warm",
"phase_time_millis" : 1565325477233,
"action" : "complete",
"action_time_millis" : 1565329539339,
"step" : "complete",
"step_time_millis" : 1565329539339,
"phase_execution" : {
"policy" : "compass-clients-policy",
"phase_definition" : {
"min_age" : "3d",
"actions" : {
"allocate" : {
"include" : { },
"exclude" : { },
"require" : {
"box_type" : "warm"
}
},
"forcemerge" : {
"max_num_segments" : 1
},
"set_priority" : {
"priority" : 50
}
}
},
"version" : 1,
"modified_date_in_millis" : 1565264841307
}
}
}
}
```
Could you explain why the block write operation has been set to the index?
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [August 12, 2019, 8:49am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/2 "2019-08-12T08:49:24Z")
Hey,
I don't see an index block here and no read-only ILM action. Did you create your own custom policy? Also, which Elasticsearch version is this?
--Alex
---
### Author:  [@worapojc](https://discuss.elastic.co/u/worapojc)
#### Post date: [August 12, 2019, 9:18am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/3 "2019-08-12T09:18:30Z")
Hi Alex, I'm using 7.2 version. I create my own policy. I also configure to force merge index in the warm phase. The number of segment is 1.
I noticed that when the index moved to warm phase. The index blocks the write operation.
---
### Author:  [@worapojc](https://discuss.elastic.co/u/worapojc)
#### Post date: [August 13, 2019, 7:44am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/4 "2019-08-13T07:44:44Z")
I think I know the cause. The force merge in warm phase will block the write operation until the force merge completed.
My indexing nodes receive the old logs from clients (\> 8 days) which should be rejected by indexing nodes but it does not.
So, it send to the warm indexes during the force merge operation.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [August 13, 2019, 9:16am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/5 "2019-08-13T09:16:29Z")
indeed, you are right. the force\_merge action sets the index to read only. I missed that in the above policy. See [https://www.elastic.co/guide/en/elasticsearch/reference/7.3/\_actions.html#ilm-forcemerge-action](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/_actions.html#ilm-forcemerge-action)
---
### Author:  [@worapojc](https://discuss.elastic.co/u/worapojc)
#### Post date: [August 13, 2019, 9:35am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/6 "2019-08-13T09:35:30Z")
This cluster is for non-production environment. I configure 1 shard and 1 replica for weekly.
Could you please suggest that should I use force merge option to move index from hot phase to warm phase?
---
### Author:  [@worapojc](https://discuss.elastic.co/u/worapojc)
#### Post date: [August 14, 2019, 9:45am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/7 "2019-08-14T09:45:32Z")
Hi, I updated my policy to do not execute force merge in warm phase.
However, it always call force merge.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 11, 2019, 9:45am UTC](https://discuss.elastic.co/t/index-blocks-write-operation-when-it-moved-to-warm-phase-by-ilm/194552/8 "2019-09-11T09:45:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.