A newer version of Hazelcast Platform is available.

View latest

Deadline Failure Detector

6.0-SNAPSHOT 5.5 5.4 5.3 5.2 5.1 5.0

Deadline Failure Detector uses an absolute timeout for missing/lost heartbeats. After timeout, a member is considered as crashed/unavailable and marked as suspected.

By default, Hazelcast uses the Deadline Failure Detector for failure detection.

The following example provides a configuration, with callouts that describe the properties:

  • XML

  • YAML

<hazelcast>
    ...
    <properties>
        <property name="hazelcast.heartbeat.failuredetector.type">deadline</property> (1)
        <property name="hazelcast.heartbeat.interval.seconds">5</property> (2)
        <property name="hazelcast.max.no.heartbeat.seconds">120</property> (3)
    </properties>
    ...
</hazelcast>
hazelcast:
  properties:
    hazelcast.heartbeat.failuredetector.type: deadline (1)
    hazelcast.heartbeat.interval.seconds: 5 (2)
    hazelcast.max.no.heartbeat.seconds: 120 (3)
1 The value must be deadline.
2 Interval at which member heartbeat messages are sent to each other.
3 Timeout that defines when a cluster member is suspect because it has not sent any heartbeats.
lifebuoy

Help and support