If Sentinel enters tilt mode without any time jump, it is likely due
to it being blocked for multiple seconds syncing the configuration on
disk, so when it is able again to enter the event loop, it discovers
an unusual time jump that can't be explained. IMHO the right fix is:
1) Check if my hypothesis is true with strace or alike.
2) Assuming 1 passes, to understand why the environment where you are
running has so poor disk performances.
Otherwise you could modify the following define:
#define SENTINEL_TILT_TRIGGER 2000
From 2 seconds (2000 milliseconds) to an higher value. However I would
not run Sentinels in an environment where to fsync from time to time
uses multiple seconds.
--
Salvatore 'antirez' Sanfilippo
open source developer - Pivotal
http://pivotal.io
"If a system is to have conceptual integrity, someone must control the
concepts."
— Fred Brooks, "The Mythical Man-Month", 1975.