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

Opster Team

Aug-23, Version: 7.14-8.9

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 the system clock on the Elasticsearch server is adjusted backwards, causing a discrepancy in time calculations. This can happen due to NTP adjustments or manual changes. To resolve this issue, you can 1) Avoid manual adjustments of the system clock. 2) Configure NTP to make smaller adjustments to the system clock. 3) Use a more reliable time source to prevent large time jumps. 4) Consider using a JVM option to reduce the impact of time adjustments.

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 ” relative clock went backwards by [{}/{}ns] 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 “relative clock went backwards by [{}/{}ns] while timer thread was sleeping” classname is ThreadPool.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        deltaNanos;
                        thresholdMillis
                    );
                } else if (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?