Recovery failed on shared filesystem – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to recover data from a shared filesystem due to issues like insufficient permissions, network connectivity problems, or disk space issues. To resolve this, you can check and adjust the permissions of the shared filesystem, ensure the network connection is stable, and verify there’s enough disk space. Additionally, check the Elasticsearch logs for more specific error messages that can guide you to the root cause. If the issue persists, consider reindexing the data or restoring from a backup.

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.

Log Context

Log “recovery failed on shared filesystem” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 // create a new IndexWriter
      "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 {
      "recovery failed on shared filesystem"; t);
            throw t;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?