Clock Offset Went Bad on a BDA 4.11 Node Even with Three NTP Servers Configured
(Doc ID 2454373.1)
Last updated on APRIL 17, 2023
Applies to:Big Data Appliance Integrated Software - Version 4.11.0 and later
On a BDA 4.11.0 / CDH 5.13.1 / OL 6.9 / Kernel 4.1.12-103.9.7.el6uek.x86_64 cluster the NTP clock offset goes bad.
In the example here the NTP clock offset went bad on one node, bdanode04, on September 24 at 9:57 PM.
When the issue occurs, messaging like below is seen in the logs:
Sep 24 9:57 PM Clock Offset Bad
Three NTP servers are configured on the cluster.
In the example here, the cluster previously had only 2 NTP servers but experienced similar problems which led to the addition of a third NTP server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document