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

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

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Un-assigning persistent tasks :” it’s important to understand a few problems related to Elasticsearch concepts persistent, plugin, upgrade. See bellow important tips and explanations on these concepts

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;




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 ElasticSearch: Unassigned Shards, how to fix?

203.11 K 152

How to stop

  91.96 K 75

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now