Logger info status – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is trying to log the status of a process or operation but encounters an issue. This could be due to a variety of reasons such as incorrect logging configurations, insufficient disk space, or permission issues. To resolve this, you can check and correct your logging configurations, ensure there is enough disk space, and verify that Elasticsearch has the necessary permissions to write to the log file. Additionally, you can also check the Elasticsearch logs for more detailed information about the error.

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

Log Context

Log “Logger.info(status);” classname is DataCountsReporter.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String status = String.format(Locale.ROOT;
                "[%s] %d records written to autodetect; missingFieldCount=%d; invalidDateCount=%d; outOfOrderCount=%d"; job.getId();
                getProcessedRecordCount(); getMissingFieldErrorCount(); getDateParseErrorsCount(); getOutOfOrderRecordCount());


        int log10TotalRecords = (int) Math.floor(Math.log10(totalRecords));
        // Start reducing the logging rate after a million records have been seen
        if (log10TotalRecords > 5) {
            logEvery = (int) Math.pow(10.0; log10TotalRecords - 5);


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?