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 run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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;
                    shard.engine().flushAndClose();
                } catch (IOException e) {
                    logger.warn("close engine failed"; e);
                    shard.failShard("failed to close engine (phase1)"; e);
                }
            }
            prepareTargetForTranslog(Translog.View.EMPTY_VIEW);
            finalizeRecovery();




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content