Log Recovery failed for primary shadow shard; failing shard – How To Solve Related Issues


Log Recovery failed for primary shadow shard; failing shard – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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 for primary shadow shard; failing shard ” 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, shard 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

Log “recovery failed for primary shadow shard; failing shard” classname is SharedFSRecoverySourceHandler.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (engineClosed) {
                // If the relocation fails then the primary is closed and can't be
                // used anymore... (because it's closed) that's a problem; so in
                // that case; fail the shard to reallocate a new IndexShard and
                // 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);
            }




 

Optimize Elasticsearch Performance

Try The Tool