Failed to write heartbeat for term %s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch is unable to write a heartbeat for a specific term, which is crucial for maintaining the health and synchronization of the cluster. This could be due to network issues, disk space problems, or node failures. To resolve this, you can check the network connectivity between nodes, ensure there is sufficient disk space, and verify the status of the nodes in the cluster. If a node is down, it should be restarted or replaced. Also, consider adjusting the cluster settings to prevent such issues in the future.

This guide will help you check for common problems that cause the log ” failed to write heartbeat for term [%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 write heartbeat for term [%s]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


                public void onFailure(Exception e) {
                    // TODO tests for heartbeat failures
                    logger.warn(() -> Strings.format("failed to write heartbeat for term [%s]"; leaderTerm); e);
                    synchronized (mutex) {
                        if (getCurrentTerm() == leaderTerm) {


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?