Reset Search
 

 

Article

Identity Engines: Unexpected Database Server Restart Caused By Hypervisor vMotion Virtual Machine Migration

« Go Back

Information

 
TitleIdentity Engines: Unexpected Database Server Restart Caused By Hypervisor vMotion Virtual Machine Migration
Symptoms

Identity Engines Ignition Server running any supported software version

VMware vMotion

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).

Environment
Cause

Ignition Server is working per design.

A vMotion transfer of an active virtual machine will disrupt HA communication between nodes resulting in dueling primary node for short period of time.

Resolution

 

VMware vMotion or any other similar virtual machine migration function is not supported by Ignition Server in standalone or HA modes.

Migration of nodes between hosts must be conducted during scheduled maintenance windows and will require hosts to be shut down, migrated and restarted. Licensing may be impacted following migration and will require new licenses for the migrated appliance.

Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255