I'm seeing time gaps in my system logs followed by this message:
Aug 18, 2016 7:08:43 AM com.hazelcast.cluster.impl.ClusterHeartbeatManager
INFO: [10.13.12.107]:7019 [topic-group_Production] [3.6] System clock apparently jumped from 2016-08-18T07:07:55.983 to 2016-08-18T07:08:43.222 since last heartbeat (+42239 ms)
so my logs have a gap in them where nothing happens for 43 seconds followed by a hazelcast message saying the system clock has jumped 43 seconds. The system clocks haven't been changed out from under my process so I was wondering if anyone else has seen this behavior. Is it possible that the Hazelcast Heartbeats can halt or disrupt a process while it waits for a response or something? Or what other sorts of problems are co-related to this.