Datafeed for jobId has seen no data in – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-7.15

Briefly, this error occurs when the Elasticsearch datafeed for a specific job ID has not received any data. This could be due to a misconfiguration in the datafeed, a problem with the data source, or a network issue. To resolve this, you can check the datafeed configuration and ensure it’s correctly set up. Also, verify the data source is operational and producing data. If it’s a network issue, check the connectivity between Elasticsearch and the data source. Lastly, check the Elasticsearch logs for any additional clues about the problem.

This guide will help you check for common problems that cause the log ” Datafeed for [” + jobId + “] has seen no data in [ ” 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 [” + jobId + “] has seen no data in [” 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);