public class OperationHeartbeatPlugin extends DiagnosticsPlugin
It does this by checking the deviation in the interval between operation-heartbeat packets. Operation-heartbeat packets are sent at a fixed interval (operation-call-timeout/4) and are not processed by operation-threads, but by their own system. If there is a big deviation, then it could indicate networking problems. But it could also indicate other problems like JVM issues.
Modifier and Type | Field and Description |
---|---|
static HazelcastProperty |
MAX_DEVIATION_PERCENTAGE
The maximum allowed deviation.
|
static HazelcastProperty |
PERIOD_SECONDS
The period in seconds this plugin runs.
|
logger
Constructor and Description |
---|
OperationHeartbeatPlugin(NodeEngineImpl nodeEngine) |
Modifier and Type | Method and Description |
---|---|
long |
getPeriodMillis()
Returns the period of executing the monitor in millis.
|
void |
onStart() |
void |
run(DiagnosticsLogWriter writer) |
public static final HazelcastProperty PERIOD_SECONDS
This plugin is very cheap to run and is enabled by default.
It will also not print output every time it is executed, only when one or more members have a too high operation-heartbeat deviation, the plugin will render output.
If set to 0, the plugin is disabled.
public static final HazelcastProperty MAX_DEVIATION_PERCENTAGE
public OperationHeartbeatPlugin(NodeEngineImpl nodeEngine)
public long getPeriodMillis()
DiagnosticsPlugin
If a monitor is disabled, 0 is returned.
If a monitor should run only once, a negative value is returned. This is
useful for 'static' monitors like the SystemPropertiesPlugin
that run at the beginning of a log file but their contents will not
change.
getPeriodMillis
in class DiagnosticsPlugin
public void onStart()
onStart
in class DiagnosticsPlugin
public void run(DiagnosticsLogWriter writer)
run
in class DiagnosticsPlugin
Copyright © 2022 Hazelcast, Inc.. All Rights Reserved.