Absolute clock went backwards by ms while timer thread was sleeping – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.14-8.9

Briefly, this error occurs when the system clock on the Elasticsearch server is adjusted backwards. Elasticsearch relies on the system clock for various operations and a backward adjustment can cause inconsistencies. To resolve this issue, you can synchronize your system clock with a Network Time Protocol (NTP) server to ensure accurate timekeeping. Also, avoid manually changing the system time. If the error persists, consider checking for any hardware issues that might be causing the system clock to drift.

This guide will help you check for common problems that cause the log ” absolute clock went backwards by [{}/{}ms] while timer thread was sleeping ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: threadpool, thread.

Log Context

Log “absolute clock went backwards by [{}/{}ms] while timer thread was sleeping” classname is ThreadPool.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                } else if (deltaMillis  thresholdNanos) {
                    final TimeValue delta = TimeValue.timeValueNanos(deltaNanos);


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?