Failed to store task result; retrying in – How to solve related issues

Average Read Time

2 Mins

Failed to store task result; retrying in – How to solve related issues

Opster Team

Jan-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 ” Failed to store task result; retrying in ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: task.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

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

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




 

Run the Check-Up to get a customized report like this:

Analyze your cluster