Failed to load started shards – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to load data from the shards that have been started. This could be due to issues like insufficient memory, disk space, or corrupted data. To resolve this, you can try increasing the memory allocation for Elasticsearch, freeing up disk space, or restoring the data from a backup. If the issue persists, you may need to rebuild the index.

This guide will help you check for common problems that cause the log ” failed to load started shards ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shards.

Log Context

Log “failed to load started shards” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return new NodeGatewayStartedShards(clusterService.localNode(); allocationId; shardStateMetadata.primary);
 logger.trace("{} no local shard info found"; shardId);
 return new NodeGatewayStartedShards(clusterService.localNode(); null; false);
 } catch (Exception e) {
 throw new ElasticsearchException("failed to load started shards"; e);
 }  public static class Request extends BaseNodesRequest {