[Pacemaker] Need help with quickstart of pacemaker on redhat

[Andrew Beekhof]

On 29/08/2013, at 7:41 PM, Moturi Upendra <moturi.upendra at gmail.com> wrote:

> Please find the attachment

The problem is that the migration-threshold has been set as a cluster option rather than a resource default.
In rhel 6.5 you'll be able to use this command:

   pcs resource defaults migration-threshold=1

In 6.4 it is:

   pcs resource rsc defaults migration-threshold=1

I'll update the quickstart now.

> 
> Thanks
> Upendra
> 
> 
> On Thu, Aug 29, 2013 at 2:55 PM, Andrew Beekhof <andrew at beekhof.net> wrote:
> Pacemaker configuration. cibadmin -Ql
> 
> Sent from a mobile device
> 
> On 29/08/2013, at 7:02 PM, Moturi Upendra <moturi.upendra at gmail.com> wrote:
> 
>> Hi,
>> 
>> here it is
>> 
>> <cluster config_version="8" name="pacemaker1">
>>   <fence_daemon/>
>>   <clusternodes>
>>     <clusternode name="node1" nodeid="1">
>>       <fence>
>>         <method name="pcmk-redirect">
>>           <device name="pcmk" port="node1"/>
>>         </method>
>>       </fence>
>>     </clusternode>
>>     <clusternode name="node2" nodeid="2">
>>       <fence>
>>         <method name="pcmk-redirect">
>>           <device name="pcmk" port="node2"/>
>>         </method>
>>       </fence>
>>     </clusternode>
>>   </clusternodes>
>>   <cman transport="udpu">
>>   </cman>
>>   <fencedevices>
>>     <fencedevice agent="fence_pcmk" name="pcmk"/>
>>   </fencedevices>
>>   <rm>
>>     <failoverdomains/>
>>     <resources/>
>>   </rm>
>> </cluster>
>> 
>> 
>> Just executed those steps in the document.
>> 
>> Thanks
>> Upendra
>> 
>> 
>> On Thu, Aug 29, 2013 at 2:59 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>> 
>> On 28/08/2013, at 8:18 PM, Moturi Upendra <moturi.upendra at gmail.com> wrote:
>> 
>> > Thank's for the reply,
>> > but as per doc it says that it has to move to different node
>> 
>> Can you show your configuration please?
>> 
>> >
>> > From the document:
>> >
>> > Simulate a Service Failure
>> >
>> > We can simulate an error by telling the service to stop directly (without telling the cluster):
>> >
>> > [ONE] # crm_resource --resource my_first_svc --force-stop
>> >
>> > If you now run crm_mon in interactive mode (the default), you should see (within the monitor interval - 2 minutes) the cluster notice that my_first_svc failed and move it to another node.
>> >
>> >
>> >
>> > thanks
>> >
>> > Upendra
>> >
>> >
>> >
>> > On Wed, Aug 28, 2013 at 3:51 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>> >
>> > On 28/08/2013, at 12:12 AM, Moturi Upendra <moturi.upendra at gmail.com> wrote:
>> >
>> > > Hi,
>> > >
>> > > I followed your article in setting up 2-node cluster with pacemaker on redhat 6.4
>> > > http://clusterlabs.org/quickstart-redhat.html
>> > >
>> > > I just executed the same steps you have mentioned in document.
>> > > When i am trying to test failure condition to start the dummy agent on node2 ,it throws an error saying the
>> > > "my_first_svc_monitor_30000 (node=node1, call=76, rc=7, status=complete): not running"
>> > >
>> > > Please help in understanding the error.
>> >
>> > Thats the cluster detecting the resource was stopped - which is expected since you stopped it.
>> >
>> 
>> 
> 
> <pcs_config.txt>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130906/327f9270/attachment-0003.sig>