Message back log has already been written – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.1-8.9

Briefly, this error occurs when Elasticsearch tries to write logs that have already been written. This could be due to a configuration issue, a bug in the software, or a problem with the underlying storage system. To resolve this issue, you could try checking and correcting the configuration settings, updating Elasticsearch to the latest version to fix any potential bugs, or investigating the storage system for any issues. Additionally, ensure that the system has enough disk space and proper permissions to write logs.

This guide will help you check for common problems that cause the log ” Message back log has already been written ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Message back log has already been written” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    protected void writeBacklog() {
        assert backlog != null;
        if (backlog == null) {
            logger.error("Message back log has already been written");

        BulkRequest bulkRequest = new BulkRequest();
        ToXContent doc = backlog.poll();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?