Log Completed deletion of expired ML data – How To Solve Related Issues


Log Completed deletion of expired ML data – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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 ” Completed deletion of expired ML data ” 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: delete and 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 “Completed deletion of expired ML data” classname is TransportDeleteExpiredDataAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             // thread is a disaster.
            remover.remove(new ThreadedActionListener(logger; threadPool; executor; nextListener; false);
                isTimedOutSupplier);
        } else {
            if (haveAllPreviousDeletionsCompleted) {
                logger.info("Completed deletion of expired ML data");
            } else {
                logger.info("Halted deletion of expired ML data until next invocation");
            }
            listener.onResponse(new DeleteExpiredDataAction.Response(haveAllPreviousDeletionsCompleted));
        }




 

Optimize Elasticsearch Performance

Try The Tool