On Wed, Nov 17, 2010 at 1:03 PM, Dejan Muhamedagic <deja...@fastmail.fm> wrote:
>> >
>> > Funny, it worked here for me every time for apache, Dummy,
>> > Delay, stonith resources. With both pacemaker 1.0 and 1.1.
>> >
>> >> To test it right now I issued a command
>> >> # crm resource restart xen_vbuild
>> >
>> > Can you try to insert a sleep and see if that helps. It's in
>> > /usr/lib64/python2.6/site-packages/crm/ui.py:
>> >
>> > 802 def restart(self,cmd,rsc):
>> > 803 "usage: restart <rsc>"
>> > 804 if not is_name_sane(rsc):
>> > 805 return False
>> > 806 if not self.stop("stop",rsc):
>> > 807 return False
>> > 808 time.sleep(1)
>> > 809 return self.start("start",rsc)
>> >
>> > Thanks,
>> >
>> > Dejan
>>
>>
>> Yep, that did the trick
>
> OK. These nodes are faster than what I have (or the other way
> around), i.e. this seems to be timing issue.
>
> Thanks,
>
> Dejan
>
well, I would say it's not normal, right? Are you going to include
this "sleep" in the stable-1.0 branch ? or maybe some op_defaults
reset_delay ?
Thanks,
Vadym
_______________________________________________
Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
