JobId failed to report datafeed timing stats – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.7-8.9

Briefly, this error occurs when Elasticsearch fails to report the timing statistics for a specific datafeed associated with a job ID. This could be due to network issues, insufficient permissions, or problems with the datafeed itself. To resolve this issue, you can try the following: 1) Check the network connectivity and ensure that Elasticsearch is properly connected. 2) Verify the permissions for the job ID and datafeed. 3) Check the health and configuration of the datafeed. 4) Restart the Elasticsearch service. 5) If the problem persists, consider reindexing the datafeed.

This guide will help you check for common problems that cause the log ” [” + jobId + “] failed to report datafeed timing stats ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[” + jobId + “] failed to report datafeed timing stats” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            persistedTimingStats = thisPersistTimingStats;
        }; e -> {
            // Since persisting datafeed timing stats is not critical; we just log a warning here.
            logger.warn(() -> "[" + jobId + "] failed to report datafeed timing stats"; e);
        if (mustWait) {


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?