no longer master while failing shard – How to solve related issues

Opster Team

Jan-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 ” no longer master while failing shard ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, master and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “{} no longer master while failing shard [{}]” classname is ShardStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         }
                    }

                    
Override
                    public void onNoLongerMaster(String source) {
                        logger.error("{} no longer master while failing shard [{}]"; request.shardId; request);
                        try {
                            channel.sendResponse(new NotMasterException(source));
                        } catch (Exception channelException) {
                            logger.warn(() ->
                                new ParameterizedMessage("{} failed to send no longer master while failing shard [{}]";



 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content