Linux Leap Second Issue
Hi,
Quick question here concerning the Linux Leap second issue. I realize that this would effect the dynaTrace Server, Analysis Server, Collector and Java agents, but would this effect other types of agents? In other words, were other types of agents such as Web Server and Host agents built using Java? And if so were they built using a JDK prior to 7u60?
Thanks!
Josh Raymond
I doubt it, unless you are running a linux kernel that is affected. From the dynatrace perspective if running agents (that's where the timing is most important) on JVMs pre 7u60 ther might be timing inaccuracies which you probably can't notice at all.
Thanks Reinhard! It sounds like the components that should be investigated for the leap second issue are as follows:
- dynaTrace Server (Frontend and Backend)
- dynaTrace Analysis Server
- dynaTrace Collectors
- dynaTrace Java Agents (Including other Java based agents such as Cassandra, Hadoop, etc)
In other words, all other agents are not a concern from the dynaTrace perspective as the impact for timing would be negligible. Our main was concern was that if the Web Server and Host agents were Java based, then they may possibly crash as well due to the Leap Second bug, causing monitoring to lost until the server is restarted.
Please let me know if I'm incorrect in any of the above statements as I plan on forwarding this information to the rest of the Guardian team and ultimately their customers.
Thanks,
Josh Raymond
Here is the according Techalert:
Technical Alerts dynaTrace DATM
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
