Identity Engines Ignition Server running any supported software version
If an Identity Engines High Availability (HA) virtual machine is migrated between hosts using VMware vMotion or any other similar virtual machine migration function, communication between active HA members will be isolated.
As a result of HA isolation each member of the HA cluster will temporarily elect itself primary database owner. Once HA connectivity has been restored and depending on the length of time each cluster member was not in communication with the other it may be required to forcibly restart the Database Server service on one of the cluster members. This ensures only one member within the cluster maintains a primary Database ownership role.
Under Dashboard -> Monitor -> Node X -> System Health one may observe the "Database Server" Last Restart or Restart Count increment one or more times during this operation.
- A troubleticket may indicate a core file has been generated during this event. This is normal as services are forcibly restarted on one node to recover from this scenario.
- dmesg output from a troubleticket may show the following event indicating a vMotion function has been performed
[<pid>]: VMCI: Updating context from (ID=<value1>) to (ID=<value2>) on event (type=0).