Log Failed to store task result; retrying in – How To Solve Related Issues

Log Failed to store task result; retrying in – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “Failed to store task result; retrying in” it’s important to understand a few problems related to Elasticsearch concepts task. See bellow important tips and explanations on these concepts

Log Context

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()) {
                } 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);

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 33764  

Spark Es Batch Write Retry Count Ne  


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now