Re: [ClusterLabs] dont (re)start a ressource if there is already running

2017-11-01 Thread Ken Gaillot
On Wed, 2017-11-01 at 16:30 +0100, Stefan Krueger wrote: > Hello, > > I've a configuration where 2nfs servers are running on different > nodes and if one node goes down move a ressources to the other one, > but dont try to restart the ressource, because it is already running. > > My config looks

[ClusterLabs] dont (re)start a ressource if there is already running

2017-11-01 Thread Stefan Krueger
Hello, I've a configuration where 2nfs servers are running on different nodes and if one node goes down move a ressources to the other one, but dont try to restart the ressource, because it is already running. My config looks like this: node 1084815873: zfs-serv1 node 1084815874: zfs-serv2

Re: [ClusterLabs] Pacemaker resource start delay when there are another resource is starting

2017-11-01 Thread Vladislav Bogdanov
01.11.2017 17:20, Ken Gaillot wrote: On Sat, 2017-10-28 at 01:11 +0800, lkxjtu wrote: Thank you for your response! This means that there shoudn't be long "sleep" in ocf script. If my service takes 10 minite from service starting to healthcheck normally, then what shoud I do? That is a tough

Re: [ClusterLabs] Pacemaker resource start delay when there are another resource is starting

2017-11-01 Thread Ken Gaillot
On Sat, 2017-10-28 at 01:11 +0800, lkxjtu wrote: > > Thank you for your response! This means that there shoudn't be long > "sleep" in ocf script. > If my service takes 10 minite from service starting to healthcheck > normally, then what shoud I do? That is a tough situation with no great answer.

Re: [ClusterLabs] different start/stop order

2017-11-01 Thread Ken Gaillot
On Wed, 2017-11-01 at 09:44 +0100, Stefan Krueger wrote: > Hello Ken, > > thanks for you help, at the moment it looks like this (its not > final): > crm(live)# conf sho > node 1084815873: zfs-serv1 > node 1084815874: zfs-serv2 > primitive HA_IP-Serv1 IPaddr2 \ > params ip=172.16.101.70

Re: [ClusterLabs] corosync race condition when node leaves immediately after joining

2017-11-01 Thread Jonathan Davies
On 31/10/17 10:41, Jan Friesse wrote: Did you get a chance to confirm whether the workaround to remove the final call to votequorum_exec_send_nodeinfo from votequorum_exec_init_fn is safe? I didn't had time to find out what exactly is happening, but I can confirm you, that workaround is

[ClusterLabs] resource "force" start / always start - how?

2017-11-01 Thread lejeczek
hi everyone question - can a resource(systemd) be configured so whenever(enable,move) cluster starts such a resource it does not care/check for it's status and always starts it? I have a service that will remain after exit and is of oneshot type, I'd like cluster to start it even if cluster

Re: [ClusterLabs] Configuring booth for multi-site cluster

2017-11-01 Thread Dejan Muhamedagic
On Tue, Oct 31, 2017 at 09:31:56AM +0100, Nicolas Huillard wrote: > Le mardi 31 octobre 2017 à 08:25 +0100, Dejan Muhamedagic a écrit : > > * is it a good idea to route the booth plain UDP/9929 traffic via > > > Internet ? (the firewalls are configured to accept only traffic > > > from/to > > >

Re: [ClusterLabs] Pacemaker resource parameter reload confusion

2017-11-01 Thread Ferenc Wágner
Ken Gaillot writes: > When an operation completes, a history entry () is added to > the pe-input file. If the agent supports reload, the entry will include > op-force-restart and op-restart-digest fields. Now I see those are > present in the vm-alder_last_0 entry, so agent