How To Solve Issues Related to Log – Failed to close translog

How To Solve Issues Related to Log – Failed to close translog

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Failed to close translog” it’s important to understand a few problems related to Elasticsearch concepts index. See bellow important tips and explanations on these concepts

Log Context

Log”Failed to close translog” classname is InternalEngine.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     logger.warn("Failed to close SearcherManager"; e);
                }
                try {
                    IOUtils.close(translog);
                } catch (Exception e) {
                    logger.warn("Failed to close translog"; e);
                }
                // no need to commit in this case!; we snapshot before we close the shard; so translog and all sync'ed
                logger.trace("rollback indexWriter");
                try {
                    indexWriter.rollback();




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 23099  

Github Issue Number 15021  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now