Failing snapshot of shard on closed node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.1

Briefly, this error occurs when Elasticsearch tries to take a snapshot of a shard located on a node that has been closed. This could be due to network issues, node failure, or improper shutdown. To resolve this, you can try restarting the node if it was improperly shut down. If the node is permanently down, you may need to reallocate the shard to an active node. Also, ensure your network connectivity is stable to prevent nodes from being unexpectedly closed.

This guide will help you check for common problems that cause the log ” failing snapshot of shard [{}] on closed node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, shard, snapshot.

Log Context

Log “failing snapshot of shard [{}] on closed node [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                if (nodes.nodeExists(shardStatus.nodeId())) {
                    shards.put(shardId; shardStatus);
                } else {
                    // TODO: Restart snapshot on another node?
                    snapshotChanged = true;
                    logger.warn("failing snapshot of shard [{}] on closed node [{}]"; shardId; shardStatus.nodeId());
                    final ShardSnapshotStatus failedState = new ShardSnapshotStatus(
                        "node shutdown";