# No rollover info found for \[filebeat-7.1.1\] with alias \[filebeat-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-filebeat-alias-the-index-has-not-yet-rolled-over-with-that-alias/200029
**Category:** Elasticsearch
**Created:** [September 18, 2019, 2:23pm UTC](https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-filebeat-alias-the-index-has-not-yet-rolled-over-with-that-alias/200029 "2019-09-18T14:23:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![krish2](https://avatars.discourse-cdn.com/v4/letter/k/b5a626/32.png) [@krish2](https://discuss.elastic.co/u/krish2)
#### Post date: [September 18, 2019, 2:23pm UTC](https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-filebeat-alias-the-index-has-not-yet-rolled-over-with-that-alias/200029/1 "2019-09-18T14:23:33Z")

</div>

## **GET filebeat-7.1.1/\_ilm/explain**

## Output:

{  
"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" : 1568730637197,  
"action" : "rollover",  
"action\_time\_millis" : 1568731141314,  
"step" : "ERROR",  
"step\_time\_millis" : 1568815741360,  
"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 } } } }

**Please find the below steps that I had followed for rollover**

## 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" } }

But it is not working as expected , Kindly help me on this.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 16, 2019, 2:23pm UTC](https://discuss.elastic.co/t/no-rollover-info-found-for-filebeat-7-1-1-with-alias-filebeat-alias-the-index-has-not-yet-rolled-over-with-that-alias/200029/2 "2019-10-16T14:23:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
