DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
HighAvailabilityManager is configurable via the following variables. Variable NameUsage| ha
| global setting | description | default value |
stop.retry. |
...
interval | The time in seconds between retries to stop or destroy a VM. | 600 |
| restart |
| .retry. |
| interval | The time |
| (in seconds) between retries to restart a VM. | 600 |
time.between.cleanup |
| The time in seconds to wait before the cleanup thread runs for the |
| different HA-Worker-Threads. The cleanup thread finds all the work items that were successful and is now ready to be purged from the the database (table: op_ha_work). | 86400 | |
| time.between.failures | Time in seconds before try to cleanup all the VMs which are registered for the HA event that were successful and are now ready to be purged. | 3600 |
max.retries | The number of times to |
try a restart for the different Work-Types: Migrating - VMs off of a host, Destroy - a VM, | 5 | |
time.to.sleep | Time in seconds to sleep if no work items are found. | 60 |
ha.workers | The number of High-Availability worker threads |
to spin off to do the processing. | 5 |
As part of the CloudStack HA design, CloudStack HA must not restart a VM if it cannot be sure that it can be done safely. In those cases, the VM stays in a transitional state. In those cases, the system administrator can manually intervene by checking to make sure the VM or the host the VM is shutdown, and then calling CloudStack to stop the VM with forced stop flag set to true. When called in this manner, CloudStack attempts to stop the VM but will continue to release resources even if any of the operations to the hypervisor host cannot be completed. After doing this, CloudStack HA will stop any attempt to restart the VM and it can be restarted by the administrator.
...