Given that the alias used for set of indices managed for ILM includes all the indices (assuming usage of the is_write_index flag), which may include frozen indices, or indices on nodes with very slow disks, it may be useful to maintain an alias which queries only the non-frozen indices.
We could add an ILM action to add and remove aliases at a certain point in the policy. For example, a policy with this action might look like the following:
PUT _ilm/policy/my_policy
{
"policy": {
"phases": {
"hot": {
"actions": {
"rollover": {
"max_age": "7d",
"max_size": "50G"
}
}
},
"cold": {
"min_age": "30d",
"actions": {
"aliases": {
"remove": ["my-ilm-alias"],
"add": ["my-ilm-alias-cold"]
},
"freeze": {}
}
},
"delete": {
"min_age": "90d",
"actions": {
"delete": {}
}
}
}
}
}
This would effectively just make a call to the Index Aliases API to add and remove the indices from the index as appropriate.
Given that the alias used for set of indices managed for ILM includes all the indices (assuming usage of the
is_write_indexflag), which may include frozen indices, or indices on nodes with very slow disks, it may be useful to maintain an alias which queries only the non-frozen indices.We could add an ILM action to add and remove aliases at a certain point in the policy. For example, a policy with this action might look like the following:
This would effectively just make a call to the Index Aliases API to add and remove the indices from the index as appropriate.