| enable |
Specifies whether to enable high availability for
VM instances. Default: true. If set to false, the high availability
feature is disabled globally. Please proceed with caution. |
true |
|
| host.check.interval |
The interval that the management node pings
abnormal hosts. Default: 5. Unit: second. |
5 |
[0,+∞) |
| host.check.maxAttempts |
The maximum number of failed connections that are
required to determine that a host is disconnected. Default:
12. |
12 |
[0,+∞) |
| host.check.successInterval |
The time period of a successful connection to a
host. Default: 5. Unit: second. If a connection request is responded
with the specified time, the connection succeeds. |
5 |
[0,+∞) |
| host.check.successRatio |
The possibility of successful connections in
contrast to failed connections that determine whether a host is
successfully connected. Default: 50. Unit: %. |
50 |
(1,99) |
| host.check.successTimes |
The minimum number of successful connections that
are required to determine that a host is successfully connected.
Default: 5. |
5 |
[0,+∞) |
| host.selfFencer.interval |
The interval that a host inspects its own status. Default: 5.
Unit: second. |
5 |
[0,+∞) |
| host.selfFencer.maxAttempts |
The maximum number of attempts that a host inspects its own
status. If the self-inspection of a host fails by the maximum
attempts, it is determined that network errors occur with the host.
Default: 6. |
6 |
[0,+∞) |
| host.selfFencer.storageChecker.timeout |
The timeout period that a host checks its connection with primary
storages. Default: 5. Unit: second. |
5 |
[0,+∞) |
| neverStopVm.retry.delay |
The delay of another retry to start up a NeverStop VM instance
after the last startup attempt fails. Default: 60. Unit:
second. |
60 |
[1,+∞) |
| neverStopVm.scan.interval |
The interval of scanning NeverStop VM instances that fail to
start up. Default: 60. Unit: second. |
60 |
[1,+∞) |
| neverStopVm.notification.times |
The synchronization speed of the state of HA VM instances on the
UI. Default: 1. Valid values: -1 to 5, integer. A higher value
indicates a lower synchronization speed. However, a higher value
lowers system loads because outdated status update notifications are
ignored. The value -1 indicates the state of HA VM instances on the
UI does not automatically change. |
1 |
[-1,5] |
| neverStopVm.gc.maxRetryIntervalTime |
The maximum interval of GC attempts to start up NeverStop VM
instances that are stopped unexpectedly. Default: 300. Unit:
second. |
300 |
[0,+∞) |
| allow.slibing.cross.clusters |
Specifies whether to enable VM migration across clusters to
achieve high availability. Default: false. If set to true, hosts
across clusters can be detected to achieve VM high availability.
Before you enable this feature, make sure that clusters are well
connected. |
false |
|
| self.fencer.strategy |
The high availability policy of VM instances. Default:
Permissive. Valid values: Permissive and Force. The value Permissive
indicates that if a VM instance is in unknown state due to primary
storage downtime, the management node does not migrate the VM
instance and the self fencer process that runs on the host does not
stop the VM instance. The value Force indicates that if the
condition that triggers high availability migration is met, the
management node migrates the VM instance to another host. |
Permissive |
|
| vm.ha.level |
Specifies whether to auto-reboot VM instances if
the VM instances are shut down due to planned maintenance or
exceptions. Valid values: none and neverstop.
- If you set the value to none, VM instances does not
auto-reboot in case of an abnormal shutdown.
- If you set the value to neverstop:
- If hosts are running properly, VM instances with HA
enabled can reboot automatically in case of an
abnormal shutdown.
- If hosts are abnormal or enter maintenance mode, VM
instances using a LocalStorage primary storage and
with HA enabled can reboot automatically in case of
an abnormal shutdown.
- If hosts are abnormal or enter maintenance mode, VM
instances using a shared storage and with HA enabled
can reboot automatically in case of an abnormal
shutdown.
 Note: You can specifically set VM HA mode for a VM instance. If
you do, this global setting does not take effect on the VM
instance. |
none |
|
