Detected new primary with primary term ; global checkpoint ; maxseqno – 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 ” Detected new primary with primary term ; global checkpoint ; maxseqno ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index 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 “Detected new primary with primary term [{}]; global checkpoint [{}]; max_seq_no [{}]” classname is IndexShard.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
                    bumpPrimaryTerm(opPrimaryTerm; () -> {
                        updateGlobalCheckpointOnReplica(globalCheckpoint; "primary term transition");
                        final long currentGlobalCheckpoint = getGlobalCheckpoint();
                        final long maxSeqNo = seqNoStats().getMaxSeqNo();
                        logger.info("detected new primary with primary term [{}]; global checkpoint [{}]; max_seq_no [{}]";
                            opPrimaryTerm; currentGlobalCheckpoint; maxSeqNo);
                        if (currentGlobalCheckpoint 

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content