My filebeat index seems to be corrupted and will not take new ingestion data. While reviewing the logs I noticed the life cycle error below over and over in the logs. The filebeat index is the only index that seems to have the issue. (Metricbeat, Functionbeat etc... are Okay) I have tried deleting the index and removing the lifecycle rule however that does not seem to resolve the issue. I am running version 7.0.0 along with Logstash for log ingestion.
Any help would be much appreciated!
# - Creating and Starting rollup jobs will no longer be allowed.
# - Stopping/Deleting existing jobs, RollupCaps API and RollupSearch continue to function.
[es/i-0/es.log] [2019-05-06T12:15:12,688][ERROR][org.elasticsearch.xpack.indexlifecycle.IndexLifecycleRunner] [instance-0000000000] policy [filebeat-7.0.0] for index [filebeat-7.0.0-2019.05.06] failed on step [{"phase":"hot","action":"rollover","name":"check-rollover-ready"}]. Moving to ERROR step
java.lang.IllegalArgumentException: index.lifecycle.rollover_alias [filebeat-7.0.0] does not point to index [filebeat-7.0.0-2019.05.06]
at org.elasticsearch.xpack.core.indexlifecycle.WaitForRolloverReadyStep.evaluateCondition(WaitForRolloverReadyStep.java:92) [x-pack-core-7.0.0.jar:7.0.0]
at org.elasticsearch.xpack.indexlifecycle.IndexLifecycleRunner.runPeriodicStep(IndexLifecycleRunner.java:133) [x-pack-ilm-7.0.0.jar:7.0.0]
at org.elasticsearch.xpack.indexlifecycle.IndexLifecycleService.triggerPolicies(IndexLifecycleService.java:270) [x-pack-ilm-7.0.0.jar:7.0.0]
at org.elasticsearch.xpack.indexlifecycle.IndexLifecycleService.triggered(IndexLifecycleService.java:213) [x-pack-ilm-7.0.0.jar:7.0.0]
at org.elasticsearch.xpack.core.scheduler.SchedulerEngine.notifyListeners(SchedulerEngine.java:168) [x-pack-core-7.0.0.jar:7.0.0]
at org.elasticsearch.xpack.core.scheduler.SchedulerEngine$ActiveSchedule.run(SchedulerEngine.java:196) [x-pack-core-7.0.0.jar:7.0.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_144]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]