Datafeed isolated immediately after reassignment – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.15-8.9

Briefly, this error occurs when Elasticsearch’s machine learning feature encounters an issue with datafeed reassignment. This could be due to network issues, node failures, or configuration problems. To resolve this, you can try the following: 1) Check the network connectivity between nodes; 2) Verify the health of the nodes and restart any that are failing; 3) Review the datafeed configuration for any errors and correct them; 4) Ensure that the Elasticsearch cluster has sufficient resources to handle the datafeed.

This guide will help you check for common problems that cause the log ” [{}] datafeed isolated immediately after reassignment. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] datafeed isolated immediately after reassignment.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            switch (datafeedTask.setDatafeedRunner(datafeedRunner)) {
                case NEITHER ->; datafeedTask::completeOrFailIfRequired);
                case ISOLATED ->"[{}] datafeed isolated immediately after reassignment."; params.getDatafeedId());
                case STOPPED -> {
          "[{}] datafeed stopped immediately after reassignment. Marking as completed"; params.getDatafeedId());


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?