THE INFORMATION IN THIS ARTICLE APPLIES TO:
- EFT v8.0 and later
DISCUSSION
The advanced property, ClusterOutOfSyncGracePeriodSecs, allows you to change the “out of sync” timeout value.
The advanced property, ClusterOutOfSyncHealSecs, allows you to change the full timeout for sync. This is the amount of time in seconds that an HA node will wait for incoming administrative messages to arrive before declaring itself to be out-of-sync with the cluster and initiating draining and restart. The default is 30 seconds. A value of 0 disables auto-draining.
These values are read upon EFT server service startup.
Specify the advanced properties described below.
{
"ClusterOutOfSyncGracePeriodSecs":"10"
"ClusterOutOfSyncHealSecs":"60"
}
Additional cluster-related advanced properties:
| Name | Type | Min | Max | Default | Description |
| ClusterCoherenceQueueDetectPrivateIP | string | 0 | 128 | autodetect | Determine whether to automatically detect private IP to advertise to other nodes. Default value is "autodetect". You can replace "autodetect" with the prefix of the IP address to find (e.g: "192.168" to match an IP address starting with 192.168). |
| ClusterCoherenceQueueMsmqType | string | 0 | 128 | msmq-multicast | Determines the type of coherence queue to use when using MSMQ. msmq-multicast uses multicast-based MSMQ queues to send administrative updates. msmq-iterative uses point-to-point MSMQ queues. Default value is msmq-multicast. |
| ClusterCoherenceQueueMulticastConfirmationTimeoutSecs | uint32_t | 0 | 2147483647 | 30 | Specifies how much time (in seconds) EFT HA cluster node should wait for own multicast MSMQ message to arrive to its own coherence queue before failing send attempt. |
| ClusterCoherenceQueueMulticastMaxRetryCount | uint32_t | 0 | 2147483647 | 5 | Specifies how much retry attempts EFT HA cluster mode should make when sending multicast MSMQ message to coherence queue. |
| ClusteredRuleHeartbeatPeriodSecs | uint32_t | 10 | 3600 | 10 | This specifies the heartbeat period in seconds for clustered event rules. The smaller the period, the sooner nodes will notice when another node has gone down, but more frequent heartbeats incur increased overhead for the production and processing of the associated event rule queue traffic. |