Log Un-assigning persistent tasks : – How To Solve Related Issues


Log Un-assigning persistent tasks : – 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 ” Un-assigning persistent tasks : ” 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: persistent, plugin and upgrade.

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 “Un-assigning persistent tasks :” classname is TransportSetUpgradeModeAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             // We want to always have the same ordering of which tasks we un-allocate first.
            // However; the order in which the distributed tasks handle the un-allocation event is not guaranteed.
            .sorted(Comparator.comparing(PersistentTask::getTaskName))
            .collect(Collectors.toList());

        logger.info("Un-assigning persistent tasks : " +
            datafeedAndJobTasks.stream().map(PersistentTask::getId).collect(Collectors.joining("; "; "[ "; " ]")));

        TypedChainTaskExecutor> chainTaskExecutor =
            new TypedChainTaskExecutor(client.threadPool().executor(executor());
                r -> true;




 

Optimize Elasticsearch Performance

Try The Tool