Failed to fetch index version after copying it over – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch fails to retrieve the index version after it has been copied. This could be due to issues with the file system, network connectivity, or insufficient permissions. To resolve this, you can try the following: 1) Check and fix any issues with your file system. 2) Ensure that your network connectivity is stable. 3) Verify that Elasticsearch has the necessary permissions to access the index files. 4) If the error persists, consider reindexing your data.

This guide will help you check for common problems that cause the log ” failed to fetch index version after copying it over ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index, version.

Log Context

Log “failed to fetch index version after copying it over” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 logger.trace("cleaning existing shard; shouldn't exists");
 si = null;
 } catch (Exception e) {
 throw new IndexShardRecoveryException(shardId; "failed to fetch index version after copying it over"; e);
 if (recoveryState.getRecoverySource().getType() == RecoverySource.Type.LOCAL_SHARDS) {
 assert indexShouldExists;
 bootstrap(indexShard; store);


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?