Datafeed for – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.6

Briefly, this error occurs when Elasticsearch’s machine learning feature is unable to retrieve data from the specified index. This could be due to incorrect datafeed configuration, missing or inaccessible index, or insufficient permissions. To resolve this, ensure the datafeed is correctly configured with the right index and query. Also, verify that the index exists and is accessible. Lastly, check the user’s permissions to ensure they have access to read from the specified index.

This guide will help you check for common problems that cause the log ” Datafeed for [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Datafeed for [” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    } catch (DatafeedJob.EmptyDataCountException e) {
                        int emptyDataCount = holder.problemTracker.reportEmptyDataCount();
                        if (e.haveEverSeenData == false && holder.shouldStopAfterEmptyData(emptyDataCount)) {
                            logger.warn("Datafeed for [" + jobId + "] has seen no data in [" + emptyDataCount
                                + "] attempts; and never seen any data previously; so stopping...");
                            // In this case we auto-close the job; as though a lookback-only datafeed stopped
                            holder.stop("no_data"; TimeValue.timeValueSeconds(20); e; true);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?