[Pacemaker] DRBD Stacked resource timeout

Miles Lott mlott at gie.com
Fri Jul 19 14:22:47 CEST 2013


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" \
        op monitor interval="31s" role="Slave" timeout="30s"

or just:
primitive DRBD_Disk1_stacked ocf:linbit:drbd \
        params drbd_resource="main-U" \
        op monitor interval="29s" timeout="30s"

Keep in mind that the 3rd node (slave on main-U) is not part of the cluster.


On 7/18/2013 11:28 PM, Andrew Beekhof wrote:
> On 19/07/2013, at 7:08 AM, Miles Lott <mlott at gie.com> 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.
>>
>> I know I can adjust the timeout on the main resource below.  My question is how might I add this to the stacked resource main-U?
> Add similar monitor operations and set timeout= as needed.
>
>



--------------------------------------------------------------------------------
Privileged, Proprietary and/or Confidential Information may be contained in
this electronic message.  If you are not the intended recipient, you should
not copy it, re-transmit it, use it or disclose its contents, but should
kindly return to the sender immediately and delete your copy from your system.
Gulf Interstate Engineering Company does not accept responsibility for
changes made to this electronic message or its attachments. 




More information about the Pacemaker mailing list