[Pacemaker] DRBD Stacked resource timeout

[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, Andrew Beekhof wrote:
> On 19/07/2013, at 10:22 PM, Miles Lott<mlott at gie.com>  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" \
>>        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"
> If it will ever become a master, then yes, you need the operations that specify a role
>
>> 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.
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-- 
Miles Lott - mlott at gie.com
Senior Systems Administrator, Houston
Gulf Interstate Engineering
ofc +1 713 375-4489
cel +1 713 899-4329



--------------------------------------------------------------------------------
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.