Created on 08-24-2015 06:32 PM - edited 09-16-2022 02:39 AM
Cloudera Community,
I have two different Cloudera Manager(CM) managed clusters that I upgraded from 5.3.3 to (5.4.1 and 5.4.3). On both clusters I get random "Clock Offset Bad" messages thoughout the day. I checked the times on all nodes and they are all in sync. I also checked the NTP configuration and it appears to be accurate. I did not have these issues when running 5.3.3. I was wondering how the CM agent checks for bad offset clock? Is there something that changed between 5.3.3 and 5.4.x?
I'm running:
Cluster 1
OS: Redhat Enterprise 6.6
CDH: 5.4.1
CM: 5.4.1
Cluster 2
OS: Redhat Enterprise 6.6
CDH: 5.4.3
CM: 5.4.3
Thanks.