after a fresh installation this log entry shows up on every node once a minute.
absolute clock went backwards by [300ms/300ms] while timer thread was sleeping
I already searched the forum and the Elasticsearch documentation but I could not find any further explanation about this error.
A google search only brings up the Elasticsearch git repository, where this error is declared.
This file has been truncated.
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
* or more contributor license agreements. Licensed under the Elastic License
* 2.0 and the Server Side Public License, v 1; you may not use this file except
* in compliance with, at your election, the Elastic License 2.0 or the Server
* Side Public License, v 1.
It seems to me, that this warning has something to do with the internal thread management.
But I could not find any hint what actually causes this warning.
NTP is configured and working on all servers.
Elasticsearch 7.16.3 / 4 Nodes
VMware ESXI 6.0
Maybe someone can provide a hint why this error is showing up.
Thank you for your help!
Really just what the message says: Elasticsearch read the system time, slept for a few hundred milliseconds, then read the time again and saw that the clock went backwards. NTP only typically introduces a clock discontinuity when it's unable to keep the clocks in sync any other way, so it sounds like something is wrong with your system's timekeeping.
Thank you for your reply. I am going to debug NTP and the system clock. As soon as I find the problem (and the solution), I am going to post it here.
Thank you for your help. The Problem was indeed caused by a misconfigured upstream ntp server.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.