Failed to bump term to %s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.9

Briefly, this error occurs when Elasticsearch tries to increase the term number of the primary shard but fails. This could be due to network issues, disk space problems, or a node failure. To resolve this issue, you can try the following: 1) Check the cluster’s health and ensure all nodes are functioning properly. 2) Verify there’s enough disk space available. 3) Check the network connectivity between nodes. 4) If the problem persists, consider restarting the Elasticsearch cluster, but be aware this could lead to downtime.

This guide will help you check for common problems that cause the log ” failed to bump term to %s ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “failed to bump term to %s” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    try {
                        logger.debug("updateMaxTermSeen: maxTermSeen = {} > currentTerm = {}; bumping term"; maxTermSeen; currentTerm);
                        ensureTermAtLeast(getLocalNode(); maxTermSeen);
                    } catch (Exception e) {
                        logger.warn(() -> format("failed to bump term to %s"; maxTermSeen); e);


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?