<br><br><div class="gmail_quote">2011/6/27 Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Jun 21, 2011 at 10:22 PM, ruslan usifov <<a href="mailto:ruslan.usifov@gmail.com">ruslan.usifov@gmail.com</a>> wrote:<br>
> No, i mean that in this constaint:<br>
><br>
> location ms_drbd_web-U_slave_on_drbd3 ms_drbd_web-U \<br>
> rule role="slave" -inf: #uname ne drbd3<br>
><br>
> pacemaker will try to start slave part of resource (if drbd3 is down) on<br>
> other nodes, but it doesn't must do that.<br>
<br>
</div>The only way to express this is to have:<br>
- a fake resource that can only run on drbd3, and<br>
- an ordering constraint tells ms_drbd_web-U to start only after the<br>
fake resource is active<br>
<br></blockquote><div><br>In future releases does this change?<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Seems like a strange setup for drbd though. Are you sure you<br>
understand how its supposed to work?<br>
<div><div></div><div class="h5"><br>
> For example on follow<br>
> configuration:<br>
><br>
> location ms_drbd_svn_slave_on_backup0 ms_drbd_svn-U \<br>
> rule role="Slave" -inf: #uname ne backup0<br>
><br>
><br>
> I see follow in failed actions:<br>
><br>
> drbd_svn-U:1_start_0 (node=storage1, call=364, rc=-2, status=Timed Out):<br>
> unknown exec error.<br>
><br>
><br>
> But as i think pacemaker doesn't must try do start actions on Slave part of<br>
> resource ms_drbd_svn-U on node storage1. And this looks like bug or perhaps<br>
> i misunderstand some things.<br>
><br>
> 2011/6/21 Andrew Beekhof <<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>><br>
>><br>
>> On Fri, Jun 17, 2011 at 9:31 AM, ruslan usifov <<a href="mailto:ruslan.usifov@gmail.com">ruslan.usifov@gmail.com</a>><br>
>> wrote:<br>
>> > Andrew does any chance to fix this behaivour??? Now this constraint<br>
>> > doesn't<br>
>> > work:<br>
>><br>
>> Define "doesn't work"?<br>
>> Not accepted by the shell? Allow's it to be started elsewhere?<br>
>> In the later case, please include a crm_report covering the time when<br>
>> ms_drbd_web-U was promoted in the incorrect location<br>
>><br>
>> ><br>
>> > location ms_drbd_web_slave_on_backup0 ms_drbd_web-U \<br>
>> > rule $id="ms_drbd_web_slave_on_backup0-rule" $role="Slave" -inf:<br>
>> > #uname ne backup0<br>
>> ><br>
>> ><br>
>> > 2011/6/8 ruslan usifov <<a href="mailto:ruslan.usifov@gmail.com">ruslan.usifov@gmail.com</a>><br>
>> >><br>
>> >> I want exactly slave role will be launch only drbd3 (stacked drbd<br>
>> >> resource). So disable launch resource on drbd3 at all not good solution<br>
>> >> for<br>
>> >> me<br>
>> >><br>
>> >> 2011/6/8 Dominik Klein <<a href="mailto:dk@in-telegence.net">dk@in-telegence.net</a>><br>
>> >>><br>
>> >>> Try without role. If the resource must not run on the node at all,<br>
>> >>> then<br>
>> >>> the role does not matter. Maybe there's a bug with role="slave"?<br>
>> >>><br>
>> >>> On 06/08/2011 10:56 AM, ruslan usifov wrote:<br>
>> >>> > i try follow:<br>
>> >>> ><br>
>> >>> > location ms_drbd_web-U_slave_on_drbd3 ms_drbd_web-U \<br>
>> >>> > rule role="slave" -inf: #uname ne drbd3<br>
>> >>> ><br>
>> >>> > result is identical, pacemaker try launch slave role on other<br>
>> >>> > nodes:-(((<br>
>> >>> ><br>
>> >>> ><br>
>> >>> > 2011/6/8 Dominik Klein <<a href="mailto:dk@in-telegence.net">dk@in-telegence.net</a><br>
>> >>> > <mailto:<a href="mailto:dk@in-telegence.net">dk@in-telegence.net</a>>><br>
>> >>> ><br>
>> >>> > >> but when i shutdown drbd3 host Pacemaker try start slave role<br>
>> >>> > on<br>
>> >>> > >> other host. How can i prevent this behavior?<br>
>> >>> > ><br>
>> >>> > > try<br>
>> >>> > > s/inf/-inf<br>
>> >>> > > s/eq/neq<br>
>> >>> ><br>
>> >>> > "ne" actually, sorry<br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>> >>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>> >>><br>
>> >>> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
>> >>> Getting started:<br>
>> >>> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
>> >>> Bugs:<br>
>> >>><br>
>> >>> <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>> ><br>
>> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
>> > Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
>> > Bugs:<br>
>> ><br>
>> > <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
>> ><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>><br>
>> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
>> Bugs:<br>
>> <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
><br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs:<br>
> <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
</div></div></blockquote></div><br>