Logger.infostatus; – How to solve related issues

Logger.infostatus; – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Logger.infostatus; ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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());

        logger.info(status);

        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);




 

Run the Check-Up to get a customized report like this:

Analyze your cluster