Copy of Cluster Failover Support

Earlier in the clustering environment, whenever a node went down, only that node could recover the process flows of that node. To overcome this, Adeptia Suite now supports Cluster failover, which means that if a node goes down then the primary node would recover the process flows of that node and would do load balancing.

For clustering failover support environment, you need to do the following:

• Create a shared recovery folder that all the nodes in the cluster can access
• All the nodes need to have full permission to access this shared recovery folder

Cluster failover support can have two scenarios:

• Secondary Node goes down
• Primary Node goes down
  
  

Secondary Node Goes Down

When the Secondary Node goes down then after a retry time of three minutes, Primary Node detects the failure and starts recovering the process flows, which were running on the Secondary Node. All the recovered process flows are also load balanced among the available nodes. If during the retry time, Secondary Node become alive, then it initiates a self-recovery.

Primary Node Goes Down

If the Primary Node goes down then after a retry time of three minutes, Secondary Node becomes the new Primary Node and starts recovering the process flows, which were running on the old Primary Node. If during the retry time, the old Primary Node become alive, then it initiates a self-recovery.

Adeptia Suite now supports email notification, which means that you get an email notification if the primary node is unable to connect with the secondary node. To enable this feature in the cluster environment, ensure that you have enabled these properties.

• Configure the time interval in property abpm.diagnostics.failure.notification.interval to trigger a check for threshold values.
• Provide the email in property abpm.diagnostics.notification.receiver.email on which you want to receive the notification.

By default, these properties are disabled. Click here to know how to enable these properties.