Detecting clock skew with Condor

Anyone who works with distributed systems knows the value of maintaining clock synchronization. Within reason of course. If you do not work with such systems, imagine debugging something by reading a trace log. The messages will be in an order you can reason about, chronological. Now imagine if the order were jumbled, or worse you did not know the order was jumbled. In a distributed system, you often have to correlate logs between systems. If the clocks are skewed it is difficult to reconstruct a timeline.

This is not a new trick, but it is one I just found useful again and thought worth sharing:

$ condor_status -master -constraint '((MyCurrentTime-LastHeardFrom) > 60) || ((MyCurrentTime-LastHeardFrom) < -60)' \
   -format "%s\t" Name \
   -format "%d\n" '(MyCurrentTime - LastHeardFrom)'
eeyore.local	75

Turns out that system has a clock about 75 seconds in the future, and did not have ntpd installed.

See also GT1671.


Tags: , ,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: