New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add note on XenServer: we depend on pool HA these days #21

Closed
wants to merge 3 commits into
base: master
from

Conversation

Projects
None yet
2 participants
@remibergsma
Copy link
Contributor

remibergsma commented May 23, 2015

Add note that we need HA on the pool in XenServer in order to recover from a pool-master crash.

We may want to add this to 4.4 and 4.5 release notes as well. Agree?

@xenserverarmy

This comment has been minimized.

Copy link

xenserverarmy commented May 23, 2015

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

@remibergsma

This comment has been minimized.

Copy link
Contributor

remibergsma commented May 24, 2015

@xenserverarmy thanks, I wanted to keep it simple and not rewrite the XenServer docs inside the CloudStack ones. BUT you're right, the timeout is not documented in the XenServer docs. So, I went ahead and put an example command and a note of the timeout. This way it's still to-the-point so people won't skip it (I hope).

@asfgit asfgit closed this in f92ec64 May 24, 2015

remibergsma added a commit to remibergsma/cloudstack-docs-rn that referenced this pull request Jun 7, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment