How To Solve Issues Related to Log – Detected new primary with primary term ; global checkpoint ; maxseqno

How To Solve Issues Related to Log – Detected new primary with primary term ; global checkpoint ; maxseqno

Updated: Jan-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 “Detected new primary with primary term ; global checkpoint ; maxseqno” it’s important to understand a few problems related to Elasticsearch concepts index, shard. See bellow important tips and explanations on these concepts

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 



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 :

1 Github Issue Number 40929  

Github Issue Number 34862  

Github Issue Number 10708

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