JobId Failed writing data counts stats – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch fails to write data count statistics for a specific job ID. This could be due to insufficient disk space, incorrect permissions, or a network connectivity issue. To resolve this, you can free up disk space, check and correct file permissions, or troubleshoot network connectivity. Additionally, ensure that the Elasticsearch cluster is properly configured and running smoothly.

This guide will help you check for common problems that cause the log ” [” + jobId + “] Failed writing data_counts 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 writing data_counts stats” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    auditor.error(jobId; "Failed persisting data_counts stats: " + e.getMessage());
        } catch (IOException e) {
            // An exception caught here basically means toXContent() failed; which should never happen
            logger.error(() -> "[" + jobId + "] Failed writing data_counts stats"; e);
            return false;
        if (mustWait) {