Persistent task with id and allocation id failed to create – How to solve related issues

Persistent task with id and allocation id failed to create – 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 ” Persistent task with id and allocation id failed to create ” 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: allocation, node, persistent and task.

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 “Persistent task [{}] with id [{}] and allocation id [{}] failed to create” classname is PersistentTasksNodeService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             }
            processed = true;
        } finally {
            if (processed == false) {
                // something went wrong - unregistering task
                logger.warn("Persistent task [{}] with id [{}] and allocation id [{}] failed to create"; task.getAction();
                        task.getPersistentTaskId(); task.getAllocationId());
                taskManager.unregister(task);
            }
        }
    }




 

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

Analyze your cluster