Menu

Search

GlobalSCAPE Knowledge Base


Registry settings for HA server drain and coherence


kmarsh
EFT Express (SMB) & Enterprise

THE INFORMATION IN THIS ARTICLE APPLIES TO:

  • EFT v7.4.2 and later

DISCUSSION

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\

DrainingTimeoutSecs

  • Type: DWORD 

  • 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.

ClusterOutOfSyncHealSecs

  • Type: DWORD 

  • 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 the service.

  • If set to 0, then do not attempt to heal; continue to operate the node out of sync.

ClusterCoherenceQueueMsmqType

  • Type: Text 

  • 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 msmq-iterative

  • To use MSMQ Broadcasting, either delete the key or set the ClusterCoherenceQueueMsmqType = msmq-broadcasting

ClusterCoherenceQueueDetectPrivateIP

  • Type: Text 

  • 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.


Also In This Category


On a scale of 1-5, please rate the helpfulness of this article


Not Helpful
Very Helpful
Optionally provide private feedback to help us improve this article...

Thank you for your feedback!


Comments require login or registration.

Details
Last Modified: 3 Months Ago
Last Modified By: kmarsh
Type: INFO
Article not rated yet.
Article has been viewed 3K times.
Options
Find Similar