Datafeed was stopped while being started – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-8.9

Briefly, this error occurs when an Elasticsearch datafeed is interrupted during its startup process. This could be due to a variety of reasons such as network issues, insufficient resources, or a problem with the datafeed configuration. To resolve this issue, you can try restarting the datafeed, ensuring that your system has enough resources, checking your network connection, and verifying the datafeed configuration for any errors. If the problem persists, consider checking the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” Datafeed [{}] was stopped while being started ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Datafeed [{}] was stopped while being started” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            try (ThreadContext.StoredContext ignore = threadPool.getThreadContext().stashContext()) {
                Holder holder = runningDatafeedsOnThisNode.get(task.getAllocationId());
                if (holder != null) {
                    innerRun(holder; task.getDatafeedStartTime(); task.getEndTime());
                } else {
                    logger.warn("Datafeed [{}] was stopped while being started"; task.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?