Github user xenserverarmy commented on the pull request:
https://github.com/apache/cloudstack-docs-rn/pull/21#issuecomment-104945193
I agree that we should add this to the 4.4 and 4.5 notes, but would suggest
an addition relating to the config-timeout. The default has changed with
XenServer version, and I don't recall it ever being 180. Text similar to the
following would alert admins to the issue of aggressive fencing with redundant
controllers.
....
Occasionally XenServer will determine that a storage heartbeat failure has
occurred and fence a host, or worse an entire pool. This typically occurs when
a redundant storage solution or a storage solution with redundant controllers
is used, and the failover timer used by the storage solution is longer than the
default XenServer HA timeout of 30 seconds. The value for this timeout can be
changed, but itâs important to know that simply enabling HA from within
XenCenter, or using the default form of the pool-enable-ha command will reset
the timeout to the default value. In the following example, the timeout has
been increased from the default to two minutes.
# xe pool-enable-ha heartbeat-sr-uuids={SR-UUID} ha-config:timeout=120
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
