JobId Failed persisting 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 save data count statistics for a specific job ID. This could be due to insufficient disk space, incorrect permissions, or network connectivity issues. To resolve this, you can check and free up disk space, verify and correct file permissions, or troubleshoot network connectivity. Additionally, ensure that the Elasticsearch cluster is properly configured and running smoothly. If the problem persists, consider checking the Elasticsearch logs for more detailed error information.

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

                () -> true;
                retryMessage -> logger.debug("[{}] Job data_counts {}"; jobId; retryMessage);
                ActionListener.wrap(r -> ongoingPersists.remove(jobId).countDown(); e -> {
                    logger.error(() -> "[" + jobId + "] Failed persisting data_counts stats"; e);
                    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


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?