Log Failing snapshot of shard on unassigned shard – How To Solve Related Issues


Log Failing snapshot of shard on unassigned shard – How To Solve Related Issues

Opster Team

Jan-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 ” Failing snapshot of shard on unassigned 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: shard, snapshot and snapshots.

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 “Failing snapshot of shard [{}] on unassigned shard [{}]” classname is SnapshotsService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         }
                    }
                }
                // Shard that we were waiting for went into unassigned state or disappeared - giving up
                snapshotChanged = true;
                logger.warn("failing snapshot of shard [{}] on unassigned shard [{}]"; shardId; shardStatus.nodeId());
                shards.put(shardId; new ShardSnapshotStatus(shardStatus.nodeId(); State.FAILED; "shard is unassigned"));
            } else {
                shards.put(shardId; shardStatus);
            }
        }




 

Optimize Elasticsearch Performance

Try The Tool