[ClusterLabs] Antw: Re: Live Guest Migration timeouts for VirtualDomain resources

>>> Ken Gaillot schrieb am 18.01.2017 um 16:32 in >>> Nachricht <4b02d3fa-4693-473b-8bed-dc98f9e3f...@redhat.com>: > On 01/17/2017 04:45 PM, Scott Greenlese wrote: >> Ken and Co, >> >> Thanks for the useful information. >> [...] >> >> Is this internally coded within the

[ClusterLabs] Colocations and Orders Syntax Changed?

Greetings! I have a lot of pacemaker clusters, each running multiple instances of mysql. I configure it so that the mysql resources are all dependent on an underlying stack of supporting resources which consists of a virtual IP address (p_vip), a filesystem (p_fs), often an LVM resource

Re: [ClusterLabs] HALVM problem with 2 nodes cluster

Marco Marino writes: > Ferenc, regarding the flag use_lvmetad in > /usr/lib/ocf/resource.d/heartbeat/LVM I read: > >> lvmetad is a daemon that caches lvm metadata to improve the >> performance of LVM commands. This daemon should never be used when >> volume groups exist

[ClusterLabs] [Announce] clufter v0.59.8 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.59.8 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Live Guest Migration timeouts for VirtualDomain resources

Dne 18.1.2017 v 16:32 Ken Gaillot napsal(a): On 01/17/2017 04:45 PM, Scott Greenlese wrote: Ken and Co, Thanks for the useful information. I bumped the migrate-to timeout value from 1200ms to 360s , which should be more than enough time to successfully migrate the resource (i.e. the KVM

Re: [ClusterLabs] Antw: Re: VirtualDomain started in two hosts

On 01/18/2017 03:49 AM, Ferenc Wágner wrote: > Ken Gaillot writes: > >> * When you move the VM, the cluster detects that it is not running on >> the node you told it to keep it running on. Because there is no >> "Stopped" monitor, the cluster doesn't immediately realize that

Re: [ClusterLabs] Live Guest Migration timeouts for VirtualDomain resources

On 01/17/2017 04:45 PM, Scott Greenlese wrote: > Ken and Co, > > Thanks for the useful information. > > I bumped the migrate-to timeout value from 1200ms to 360s , which should > be more than enough time > to successfully migrate the resource (i.e. the KVM guest). The migration > was again

Re: [ClusterLabs] HALVM problem with 2 nodes cluster

Ferenc, regarding the flag use_lvmetad in /usr/lib/ocf/resource.d/heartbeat/LVM I read: "#lvmetad is a daemon that caches lvm metadata to improve the # performance of LVM commands. This daemon should never be used when # volume groups exist that are being managed by the

Re: [ClusterLabs] HALVM problem with 2 nodes cluster

Marco Marino writes: > I agree with you for > use_lvmetad = 0 (setting it = 1 in a clustered environment is an error) Where does this information come from? AFAIK, if locking_type=3 (LVM uses internal clustered locking, that is, clvmd), lvmetad is not used anyway, even if

Re: [ClusterLabs] Antw: how do you do your Samba?

On 17/01/17 15:59, Ulrich Windl wrote: lejeczek schrieb am 17.01.2017 um 16:27 in Nachricht : hi everyone asking here as I hope experts here have already done it dozens times. I've gotten a nice answer from samba

Re: [ClusterLabs] Antw: Re: VirtualDomain started in two hosts

Ken Gaillot writes: > * When you move the VM, the cluster detects that it is not running on > the node you told it to keep it running on. Because there is no > "Stopped" monitor, the cluster doesn't immediately realize that a new > rogue instance is running on another node.

Re: [ClusterLabs] HALVM problem with 2 nodes cluster

Hi Bliu, thank you. I agree with you for use_lvmetad = 0 (setting it = 1 in a clustered environment is an error) but I think I have to set locking_type = 3 only if I use clvm In my case, I'm trying to use LVM so I think that locking_type = 1 is ok. What do you think about? Furthermore, I have an

Re: [ClusterLabs] HALVM problem with 2 nodes cluster

On 01/18/2017 04:45 PM, Marco Marino wrote: Hi, I'm trying to realize a cluster with 2 nodes that manages a volume group. Basically I have a san connected to both nodes that exposes 1 lun. So both nodes have a disk /dev/sdb. From one node I did: fdisk /dev/sdb <- Create a partition with

[ClusterLabs] HALVM problem with 2 nodes cluster

Hi, I'm trying to realize a cluster with 2 nodes that manages a volume group. Basically I have a san connected to both nodes that exposes 1 lun. So both nodes have a disk /dev/sdb. From one node I did: fdisk /dev/sdb <- Create a partition with type = 8e (LVM) pvcreate /dev/sdb1 vgcreate myvg