Bug report
Elasticsearch version
7.2.0 and 7.3.1 ESS
Description of the problem including expected versus actual behavior:
When I look at my indices under index management and apply the Lifecycle filters (hot, warm, cold) I see that I have a bunch of Filebeat indices that are not in any of the above states. When I look at the details I see the state is "completed":
Using the following ILM policy index should go to "warm" on rollover:
{
"policy": {
"phases": {
"hot": {
"min_age": "0ms",
"actions": {
"rollover": {
"max_age": "1h",
"max_size": "50mb",
"max_docs": 100
}
}
},
"warm": {
"min_age": "1h",
"actions": {
"allocate": {
"include": {},
"exclude": {},
"require": {
"data": "warm"
}
}
}
}
}
}
}
Steps to reproduce:
- Run
filebeat setup
- Edit ILM policy to reduce time (so you do not have to wait 30 days)
- Run
filebeat
- Wait for rollover
Bug report
Elasticsearch version
7.2.0 and 7.3.1 ESS
Description of the problem including expected versus actual behavior:
When I look at my indices under index management and apply the Lifecycle filters (hot, warm, cold) I see that I have a bunch of Filebeat indices that are not in any of the above states. When I look at the details I see the state is "completed":
Using the following ILM policy index should go to "warm" on rollover:
Steps to reproduce:
filebeat setupfilebeat