Re: [Pacemaker] DRBD Stacked resource timeout

2013-07-22 Thread Miles Lott
I suppose that since one of the two servers in the cluster will be master that I only need this line. The only possible slave (3rd node) is not in the cluster, so I am guessing that I don't need that config: op monitor interval="29s" role="Master" timeout="30s" On 07/21/2013 10:11 PM, Andre

Re: [Pacemaker] DRBD Stacked resource timeout

2013-07-21 Thread Andrew Beekhof
On 19/07/2013, at 10:22 PM, Miles Lott wrote: > Thanks. That seemed ok but I had not seen an example of it done on a stacked > resource. One more question: Would I need to add monitors such as: > > primitive DRBD_Disk1_stacked ocf:linbit:drbd \ > params drbd_resource="main-U" \ >

Re: [Pacemaker] DRBD Stacked resource timeout

2013-07-19 Thread Miles Lott
Thanks. That seemed ok but I had not seen an example of it done on a stacked resource. One more question: Would I need to add monitors such as: primitive DRBD_Disk1_stacked ocf:linbit:drbd \ params drbd_resource="main-U" \ op monitor interval="29s" role="Master" timeout="30s" \

Re: [Pacemaker] DRBD Stacked resource timeout

2013-07-18 Thread Andrew Beekhof
On 19/07/2013, at 7:08 AM, Miles Lott wrote: > This is the part of our pacemaker config which sets up our primary/secondary > drbd resource as well as the stacked resource. Due to occasional load on the > server, the resource check will timeout, forcing a reboot of the node using > ipmi. > >

[Pacemaker] DRBD Stacked resource timeout

2013-07-18 Thread Miles Lott
This is the part of our pacemaker config which sets up our primary/secondary drbd resource as well as the stacked resource. Due to occasional load on the server, the resource check will timeout, forcing a reboot of the node using ipmi. I know I can adjust the timeout on the main resource below