Failed to roll translog generation – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to roll to the next translog generation, which is crucial for data recovery and consistency. This could be due to insufficient disk space, file system issues, or a bug in Elasticsearch. To resolve this, you can try freeing up disk space, checking the file system for errors, or upgrading Elasticsearch to the latest stable version. If the issue persists, you may need to rebuild the index from your data source.

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

Log Context

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

                    logger.debug("submitting async roll translog generation request");
                    final AbstractRunnable roll = new AbstractRunnable() {
                        public void onFailure(final Exception e) {
                            if (state != IndexShardState.CLOSED) {
                                logger.warn("failed to roll translog generation"; e);

                        protected void doRun() {