How To Solve Issues Related to Log – Failed to derived initial-shards from value ; ignore allocation for

How To Solve Issues Related to Log – Failed to derived initial-shards from value ; ignore allocation for

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Failed to derived initial-shards from value ; ignore allocation for” it’s important to understand a few problems related to Elasticsearch concepts allocation, shard. See bellow important tips and explanations on these concepts

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;
    }




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

 

   

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now