Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

...

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.

Info

You can configure the retry time in the server-configure.properties file.

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.

Info

You can configure the retry time in the server-configure.properties file.


You get an email notification if the primary node is unable to connect with the secondary node and crossed the configured threshold values. To enable this featurecan also set up receiving mail notification from Adeptia Suite in case any node in a cluster goes down. To receive notification email, ensure that you have enabled these properties to set the threshold values.the following properties:

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

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