Cannot start datafeed – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to start a datafeed due to issues like incorrect datafeed configuration, insufficient permissions, or unavailability of the target index. To resolve this, ensure that the datafeed configuration is correct and the target index exists. Also, check if the user has the necessary permissions to start the datafeed. If the issue persists, consider restarting the Elasticsearch cluster.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” cannot start datafeed [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “cannot start datafeed [” class name is TransportStartDatafeedAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 @Override
 public void onFailure(Exception e) {
 if (ExceptionsHelper.unwrapCause(e) instanceof ResourceAlreadyExistsException) {
 logger.debug("datafeed already started"; e);
 e = new ElasticsearchStatusException("cannot start datafeed [" + params.getDatafeedId() +
 "] because it has already been started"; RestStatus.CONFLICT);
 }
 listener.onFailure(e);
 }
 };

 

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?