Log Close engine failed – How To Solve Related Issues

Log Close engine failed – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Close engine failed” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: handler, indices, recovery, source.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”close engine failed” classname is SharedFSRecoverySourceHandler.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     // if we relocate we need to close the engine in order to open a new
                    // IndexWriter on the other end of the relocation
                    engineClosed = true;
                } catch (IOException e) {
                    logger.warn("close engine failed"; e);
                    shard.failShard("failed to close engine (phase1)"; e);


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 18508  

Failed To Recover From Translog Cur  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now