Datafeed stopped immediately after reassignment Marking as completed – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.15-8.9

Briefly, this error occurs when an Elasticsearch datafeed stops functioning right after it has been reassigned. This could be due to a variety of reasons such as network issues, insufficient resources, or configuration errors. To resolve this issue, you can try the following: 1) Check the network connectivity and ensure that there are no interruptions. 2) Verify that the Elasticsearch cluster has enough resources to handle the datafeed. 3) Review the datafeed configuration and correct any errors. 4) Restart the datafeed and monitor its performance closely.

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

Log Context

Log “[{}] datafeed stopped immediately after reassignment. Marking as completed” 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?