# No rollover info found for \[filebeat-7.1.1\] with alias , the index has not yet rolled over with that alias
**URL:** https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-the-index-has-not-yet-rolled-over-with-that-alias/201808
**Category:** Elasticsearch
**Created:** [October 1, 2019, 1:21pm UTC](https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-the-index-has-not-yet-rolled-over-with-that-alias/201808 "2019-10-01T13:21:16Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@krish2](https://discuss.elastic.co/u/krish2)
#### Post date: [October 1, 2019, 1:21pm UTC](https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-the-index-has-not-yet-rolled-over-with-that-alias/201808/1 "2019-10-01T13:21:16Z")
When I run the command "GET filebeat-7.1.1/\_ilm/explain" in Kibana console I am getting the below error .
{
"indices" : {
"filebeat-7.1.1" : {
"index" : "filebeat-7.1.1",
"managed" : true,
"policy" : "new\_policy\_1",
"lifecycle\_date\_millis" : 1566224013121,
"phase" : "hot",
"phase\_time\_millis" : 1569506868505,
"action" : "rollover",
"action\_time\_millis" : 1569506941341,
"step" : "ERROR",
"step\_time\_millis" : 1569584341468,
"failed\_step" : "update-rollover-lifecycle-date",
"step\_info" : {
"type" : "illegal\_state\_exception",
"reason" : "no rollover info found for [filebeat-7.1.1] with alias [filebeat-alias], the index has not yet rolled over with that alias",
"stack\_trace" : """
java.lang.IllegalStateException: no rollover info found for [filebeat-7.1.1] with alias [filebeat-alias], the index has not yet rolled over with that alias
at org.elasticsearch.xpack.core.indexlifecycle.UpdateRolloverLifecycleDateStep.performAction(UpdateRolloverLifecycleDateStep.java:58)
at org.elasticsearch.xpack.indexlifecycle.ExecuteStepsUpdateTask.execute(ExecuteStepsUpdateTask.java:95)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:47)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:687)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:310)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:210)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:142)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:252)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:215)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:835)
"""
},
"phase\_execution" : {
"policy" : "new\_policy\_1",
"phase\_definition" : {
"min\_age" : "0ms",
"actions" : {
"rollover" : {
"max\_size" : "10gb",
"max\_age" : "1d"
}
}
},
"version" : 1,
"modified\_date\_in\_millis" : 1568361450082
}
}
}
}
I followed the below steps:
## Setting up an ILM policy :
PUT \_ilm/policy/new\_policy\_1
{
"policy": {
"phases": {
"hot": {
"actions": {
"rollover": {
"max\_age": "1d",
"max\_size": "10gb"
}
}
}
}
}
}
## To create alias for index:
POST /\_aliases
{
"actions" : [
{ "add" : { "index" : "filebeat-7.1.1", "alias" : "filebeat-alias" } }
]
}
## Bootstrapping with new index:
PUT /%3Cfilebeat-%7Bnow%2Fs%7Byyyy-MM-dd-HH-mm-ss%7D%7D-1%3E
{
"aliases": {
"filebeat-alias":{
"is\_write\_index": true
}
}
}
## Applying a policy to our index:
PUT \_template/filebeat-7.1.1
{
"index\_patterns": ["filebeat-\*"],
"settings": {
"number\_of\_shards": 1,
"number\_of\_replicas": 1,
"index.lifecycle.name": "new\_policy\_1",
"index.lifecycle.rollover\_alias": "filebeat-alias"
}
}
* * *
PUT /\_cluster/settings
{
"persistent": {
"action.auto\_create\_index": true
}
}
POST /filebeat-alias/\_rollover
{
"conditions": {
"max\_age": "1d",
"max\_size": "10gb"
}
}
Kindly help me on this.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 29, 2019, 1:21pm UTC](https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-the-index-has-not-yet-rolled-over-with-that-alias/201808/2 "2019-10-29T13:21:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.