The hot phase is an index lifecycle stage in which an index stays fully operational for both indexing and querying. It is normally the starting phase, but an index may remain hot or transition to another lifecycle phase. section 6.9.1
Use the hot phase to control active index operations:
- Keep an index available for normal reads and writes. section 6.9.1
- Delay actions with min_age, such as setting recovery priority after one day. section 6.9.2
- Roll over time-series indexes when age, document count, or size reaches a configured limit. section 6.9.3
- Move indexes to warm, cold, frozen, or delete phases when the policy requires it. section 6.9.1
Rollover an active MySQL log index
A hot-only policy can start immediately and roll over an index after one day, 10,000 documents, or 10 GB. Attach the policy and rollover alias through an index template, then mark the initial index as the alias's writable index. section 6.9.3
Listing 6.50 Simple policy definition for the hot phase
PUT _ilm/policy/hot_simple_policy
{
"policy": {
"phases": {
"hot": { #1
"min_age": "0ms", #2
"actions": {
"rollover": { #3
"max_age": "1d",
"max_docs": 10000,
"max_size": "10gb"
}
}
}
}
}
}
Shows a runnable ILM policy that enters the hot phase immediately and applies rollover limits. section 6.9.3
Listing 6.48 Creating a policy with hot and delete phases
PUT _ilm/policy/hot_delete_policy #1
{
"policy": { #2
"phases": {
"hot": { #3
"min_age": "1d", #4
"actions": { #5
"set_priority": { #6
"priority": 250
}
}
},
"delete": { #7
"actions": {
"delete" : { }
}
}
}
}
}
Shows a policy that keeps an index hot for one day, sets recovery priority, and then deletes it. section 6.9.2
