THE INFORMATION IN THIS ARTICLE APPLIES TO:
- EFT v7.4.2 and later
- EFT v4.x to v7.4.x stores advanced properties in the registry.
- EFT v8.x stores Advanced Properties in a JSON file.
- When you upgrade from EFT v7.4.x to EFT v8, the non-default settings that you have defined in the registry will be added to the Advanced Properties file during upgrade. (Default settings are part of the EFT configuration files.)
Please refer to the EFT help for a spreadsheet of advanced properties for your version of EFT.
The following registry settings for HA server drain and coherence should be created in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 7.4\
Draining timeout in seconds allows you to adjust the time for ongoing event rules and transfers to complete before draining starts.
Default is 900 seconds (15 minutes).
Maximum is 86400 seconds (24 hours).
If set to 0, then immediately shutdown and do not drain.
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.
Default is 30 seconds.
If out of sync is detected, the node attempts to heal; if it
can heal within the timeout period, the system resyncs and continues
to operate as expected.
If out of sync is detected and cannot be repaired within the
heal timeout period, the node will enter drain mode and then restart
If set to 0, then do not attempt to heal; continue to operate
the node out of sync.
By default the MSMQ Broadcasting will be the default. TCP method
of broadcasting ftp.cfg changes was developed for environments that
do not support multicast (e.g., Azure and vMotion). Although AWS does
not support Multicast, this was developed prior to the support of
this option and so uses the AWS SQS/SNS services for now.
To use the TCP instead of MSMQ Broadcasting, set the Advanced
Registry key ClusterCoherenceQueueMsmqType
To use MSMQ Broadcasting, either delete the key or set the ClusterCoherenceQueueMsmqType =
Used to explicitly define the IP/Subnet via registry entry/advanced property, localized per node.
It can either be set to autodetect (which is the default, which
causes it to find and use the first private subnet it finds), or it
can be set to the prefix of the interface to use (e.g., “192.168.0",
"192.168." or "192.168" just the prefix of the
subnet, with no quotes).
Changes made in the registry are recorded in the ActiveNodes.json
(located in the HA cluster's Shared configuration folder), which is
used automatically by the EFT nodes to pass information between themselves
and should not be edited.
If you do not choose to use the default subnet on a particular
EFT node, that node will simply place the IP address you put for the
advanced properties key in the “IP” field. That IP address will be
the one the other nodes use to try to talk to it.
When HaErrorHandler is recovering from an error, should it drain the server before restarting?
Default value: false
Determines if EFT should shutdown the HTTP/S server socket(s) immediately upon entering draining.