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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

Log Context

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;
        }
    }





 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content