I noticed that the Shrink ILM operation makes the source & target index read only, which make sense because that's a requirement for a shrink even if done manually. The issue is that my shrinked index remains read only after the ILM as completed its work.
This is unexpected to me, the documentation (and the ILM page on Kibana) does not really mention that. It says "Sets a source index to read-only and shrinks it into a new index with fewer primary shards" but does not indicate that the shrinked index will remain read only. Besided, the shrink operation is only available when moving to the warm phase, which is supposed to still allow for updates (in my case vary rare, but can happen).
So it looks like a bug or missing feature but I would like to be sure before opening an issue.
Here is my policy:
{
"policy": {
"phases": {
"hot": {
"min_age": "0ms",
"actions": {
"set_priority": {
"priority": 100
}
}
},
"warm": {
"min_age": "60d",
"actions": {
"forcemerge": {
"max_num_segments": 1,
"index_codec": "best_compression"
},
"set_priority": {
"priority": 50
},
"shrink": {
"max_primary_shard_size": "50gb"
},
"allocate": {
"number_of_replicas": 1
}
}
},
"cold": {
"min_age": "740d",
"actions": {
"set_priority": {
"priority": 10
}
}
}
}
}
}