[OO Support Tip] How to make a flow executed on a cluster resume on a different node
When using a Terracotta cluster in OO, if node1 dies, the flows being executed on it become orphaned. By default, those are not resumed on node2. There is a way of making them automatically be resumed on the active node (node2).
For a Clustered OO deployment, login to Central User Interface (UI) -> Administration tab -> System Configuration sub-tab -> set “Automatically resume orphaned headless runs from a Central failure” to true and save. Then all Central servers in cluster must be restarted. Confirm the same setting has automatically been replicated to other Central servers in the cluster.
When one Central server running a workflow dies, you can observe this workflow using the Central UI on another server in the cluster. At first the workflow goes into an “Orphan” state. Then after a few minutes (usually between 2 - 10 minutes) the workflow goes back into a “Go” state and continues running on the remaining Central server in the cluster.
Here is the original document:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.