Failed to derived initial-shards from value ; ignore allocation for – How to solve related issues

Failed to derived initial-shards from value ; ignore allocation for – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Failed to derived initial-shards from value ; ignore allocation for ” 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: allocation and shard.

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 “[{}][{}] failed to derived initial_shards from value {}; ignore allocation for {}” classname is PrimaryShardAllocator.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     }
                } else {
                    requiredAllocation = Integer.parseInt(initialShards);
                }
            } catch (Exception e) {
                logger.warn("[{}][{}] failed to derived initial_shards from value {}; ignore allocation for {}"; shard.index(); shard.id(); initialShards; shard);
            }
        }

        return nodesAndVersions.allocationsFound >= requiredAllocation;
    }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster