Failed to store task result retrying in – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.2

Briefly, this error occurs when Elasticsearch is unable to store the result of a task due to issues like insufficient disk space, network connectivity problems, or permission issues. To resolve this, you can check if there’s enough disk space and clean up if necessary. Also, ensure that Elasticsearch has the necessary permissions to write to the directory. Lastly, check your network connectivity to ensure that Elasticsearch can communicate with the storage system.

This guide will help you check for common problems that cause the log ” failed to store task result; retrying in [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task.

Log Context

Log “failed to store task result; retrying in [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            public void onFailure(Exception e) {
                if (false == (e instanceof EsRejectedExecutionException) || false == backoff.hasNext()) {
                } else {
                    TimeValue wait =;
                    logger.warn(() -> new ParameterizedMessage("failed to store task result; retrying in [{}]"; wait); e);
                    threadPool.schedule(() -> doStoreResult(backoff; index; listener); wait; ThreadPool.Names.SAME);


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?