How To Solve Issues Related to Log – Persistent task with id and allocation id failed to create

How To Solve Issues Related to Log – Persistent task with id and allocation id failed to create

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Persistent task with id and allocation id failed to create” it’s important to understand a few problems related to Elasticsearch concepts allocation, node, persistent, task. See bellow important tips and explanations on these concepts

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




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 44566  

Github Issue Number 37545  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now