Persistent task – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Persistent task ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, persistent and task.


Log Context

Log “Persistent task” classname is PersistentTasksClusterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

      * 
param listener     the listener that will be called when task is removed
     */
    public void completePersistentTask(String id; long allocationId; Exception failure; ActionListener> listener) {
        final String source;
        if (failure != null) {
            logger.warn("persistent task " + id + " failed"; failure);
            source = "finish persistent task (failed)";
        } else {
            source = "finish persistent task (success)";
        }
        clusterService.submitStateUpdateTask(source; new ClusterStateUpdateTask() {



 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content