Recovery failed on shared filesystem – How to solve related issues

Average Read Time

2 Mins

Recovery failed on shared filesystem – 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 ” Recovery failed on shared filesystem ” 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: handler, 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 “recovery failed on shared filesystem” classname is SharedFSRecoverySourceHandler.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 // create a new IndexWriter
                logger.info("recovery failed for primary shadow shard; failing shard");
                // pass the failure as null; as we want to ensure the store is not marked as corrupted
                shard.failShard("primary relocation failed on shared filesystem caused by: [" + t.getMessage() + "]"; null);
            } else {
                logger.info("recovery failed on shared filesystem"; t);
            }
            throw t;
        }
    }





 

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

Analyze your cluster