PhixFlow con be configured as a multiple-instance cluster in which at any one time, one instance is the main, active instance and the other instance(s) serve as hot standbys – if the main instance fails, one of the standby instances will automatically take over as the active instance.
The different instances must run on separate Java virtual machines, and will generally run on separate physical servers.
...
Configuring a resilient instance
A resilient PhixFlow configuration consists of 2 or more web applications all connected to a common database and configured such that at any one time, only one is active; the other instances will monitor the first and one will take over if they detect that the first has failed.
In such a configuration, set the instance name and id for each PhixFlow webapp instance to unique values and set leaderOnStartup to “true” for an instance if it should become active immediately on startup.
When configuring instances in a resilient configuration, edit the phixflow-clusterinstance.xml file for each instance so that
...
b) The main instance has leaderOnStartup set to true, and the standby instance has it set to false.
Each phixflow-instance.xml should look something like this:
| Code Block |
|---|
<!-- The instance name must be different for each member of the cluster -->
<bean id="clusterInstance"
class="com.accipia.phixflow.service.cluster.main.ClusterInstance"
p:name="MAIN"
p:id=”1”
p:leaderOnStartup="true"
/> |
If no instance has leaderOnStartup set to true, one of the standby servers will become active after a timeout period..
...