No known data frame analytics with id – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.3-8.9

Briefly, this error occurs when Elasticsearch cannot find a data frame analytics job with the specified ID. This could be due to a typo in the ID, or the job may have been deleted. To resolve this issue, you can verify the ID of the data frame analytics job you’re trying to access. If the ID is correct, check if the job exists in your Elasticsearch cluster. If it doesn’t, you may need to recreate the job. If the job does exist, there may be a problem with your Elasticsearch cluster’s state, which may require a restart or further troubleshooting.

This guide will help you check for common problems that cause the log ” No known data frame analytics with id [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “No known data frame analytics with id [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public static ResourceAlreadyExistsException datafeedAlreadyExists(String datafeedId) {
 return new ResourceAlreadyExistsException(Messages.getMessage(Messages.DATAFEED_ID_ALREADY_TAKEN; datafeedId));
 }  public static ResourceNotFoundException missingDataFrameAnalytics(String id) {
 return new ResourceNotFoundException("No known data frame analytics with id [{}]"; id);
 }  public static ResourceAlreadyExistsException dataFrameAnalyticsAlreadyExists(String id) {
 return new ResourceAlreadyExistsException("A data frame analytics with id [{}] already exists"; id);