Failed to create local checkpoint tracker – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.2

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch fails to create a local checkpoint tracker, which is crucial for tracking the indexing operations. This could be due to insufficient disk space, corrupted indices, or network issues. To resolve this, you can try freeing up disk space, checking the health of your indices and repairing if necessary, or troubleshooting your network. Additionally, ensure that your Elasticsearch version is up-to-date and compatible with your system.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” failed to create local checkpoint tracker ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “failed to create local checkpoint tracker” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return tracker;
 } catch (IOException ex) {
 throw new EngineCreationFailureException(engineConfig.getShardId(); "failed to create local checkpoint tracker"; ex);
 }  private SoftDeletesPolicy newSoftDeletesPolicy() throws IOException {
 final Map commitUserData = store.readLastCommittedSegmentsInfo().userData;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?