Failed to send error back to recovery source – How to solve related issues

Average Read Time

2 Mins

Failed to send error back to recovery source – How to solve related issues

Opster Team

Feb-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 send error back to recovery source ” 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: indices, recovery and source.

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 send error back to recovery source” classname is RecoveryTarget.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
                        protected void onFailure(Exception e) {
                            try {
                                channel.sendResponse(e);
                            } catch (IOException e1) {
                                logger.warn("failed to send error back to recovery source"; e1);
                            }
                        }

                        
Override
                        public void onClusterServiceClose() {



 

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

Analyze your cluster