[
https://issues.apache.org/jira/browse/CLOUDSTACK-8628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625884#comment-14625884
]
ASF GitHub Bot commented on CLOUDSTACK-8628:
--------------------------------------------
GitHub user wido opened a pull request:
https://github.com/apache/cloudstack/pull/580
CLOUDSTACK-8628: kvm: Disable Fencing when no NFS storage pools are p…
…resent
On NFS we write a heartbeat, but without those we can not safely
fence off a host.
If we fence without knowing about a heartbeat we can cause a split-brain
situation.
Signed-off-by: Wido den Hollander <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wido/cloudstack CLOUDSTACK-8628
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/580.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #580
----
commit dea553ec69831661bd40237db0c18c4dcd1f86e6
Author: Wido den Hollander <[email protected]>
Date: 2015-07-13T15:26:00Z
CLOUDSTACK-8628: kvm: Disable Fencing when no NFS storage pools are present
On NFS we write a heartbeat, but without those we can not safely
fence off a host.
If we fence without knowing about a heartbeat we can cause a split-brain
situation.
Signed-off-by: Wido den Hollander <[email protected]>
----
> Ceph RBD only cluster with KVM does not fence properly
> ------------------------------------------------------
>
> Key: CLOUDSTACK-8628
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8628
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Wido den Hollander
> Assignee: Wido den Hollander
> Fix For: Future, 4.6.0
>
>
> When a NFS storage pool is present on a KVM cluster that pool is used for
> writing heartbeats to.
> In case of a Ceph (RBD) only cluster such pools are not available and thus
> the KVM hosts do not write any heartbeats.
> Should the KVM Agent crash for any reason they will be fenced of directly and
> this will cause a split-brain situation.
> Fencing should not happen when no NFS storage pool is present as it is
> dangerous for data consistency. A Instance could be running on two hosts at
> the same time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
