Halted deletion of expired ML data until next invocation – How to solve related issues

Average Read Time

2 Mins

Halted deletion of expired ML data until next invocation – 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 ” Halted deletion of expired ML data until next invocation ” to appear. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Halted deletion of expired ML data until next invocation” classname is TransportDeleteExpiredDataAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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




 

Try AutoOps to detect and fix issues in your cluster:

Watch Product Tour

Get Started Free

Skip to content