Failed to create engine – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” failed to create engine ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “failed to create engine”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final Map commitData = commitDataAsMap(writer);
 historyUUID = loadHistoryUUID(commitData);
 forceMergeUUID = commitData.get(FORCE_MERGE_UUID_KEY);
 indexWriter = writer;
 } catch (IOException | TranslogCorruptedException e) {
 throw new EngineCreationFailureException(shardId; "failed to create engine"; e);
 } catch (AssertionError e) {
 // IndexWriter throws AssertionError on init; if asserts are enabled; if any files don't exist; but tests that
 // randomly throw FNFE/NSFE can also hit this:
 if (ExceptionsHelper.stackTrace(e).contains("org.apache.lucene.index.IndexWriter.filesExist")) {
 throw new EngineCreationFailureException(shardId; "failed to create engine"; e);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content