Thank u lars!<div><br></div><div>I've implemented a cron scripts that if found drbd in Unconfigured state do a service reload. With this workaruond all seems to work fine.</div><div><br></div><div>But... if the service really switch on other node and, for a reason, it come back to last nod what happen?</div>
<div><br></div><div>It is very strange... it need a manual restart however.</div><div><br></div><div>Simone</div><div><br><div class="gmail_quote">2013/2/26 Lars Ellenberg <span dir="ltr"><<a href="mailto:lars.ellenberg@linbit.com" target="_blank">lars.ellenberg@linbit.com</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 Fri, Feb 22, 2013 at 11:26:07AM +0100, Simone Del Pinto wrote:<br>
> Hi guys,<br>
><br>
> we are using drbd 8.3.13 on our 2 linux server to keep data of the oer MySQL server.<br>
><br>
> corosync and pacemaker ensure that we have a virtuel IP running and that our DB is always up on one of those nodes.<br>
> During a failover test we noted that when we put the Master node in standy<br>
> ( crm node standby )<br>
<br>
</div>"crm node standby" means: stop all services on that node.<br>
stop means stop.<br>
stop of DRBD means taking it down.<br>
<br>
there is no "native" way to<br>
tell pacemaker to "go standby but leave DRBD configured as Secondary".<br>
<br>
There are a few ways to achieve similar functionality, though.<br>
You could do implement that using constraints,<br>
possibly referencing node attributes.<br>
<br>
<br>
Or you re-configure drbd by hand<br>
once you switched to standby in pacemaker,<br>
just as you apparently did already.<br>
<div class="im"><br>
> all services switch to other node but DRBD goes in "Unconfigured state".<br>
> Below the situation before standby:<br>
><br>
> crm_mon -V1<br>
</div><div class="im">> Master/Slave Set: ms_zends_drbd [p_zends_drbd]<br>
> Masters: [ FRCVD2046 ]<br>
> Slaves: [ FRCVD2047 ]<br>
><br>
> Now the situation after "crm node standby":<br>
><br>
</div><div class="im">> Master/Slave Set: ms_zends_drbd [p_zends_drbd]<br>
> Masters: [ FRCVD2047 ]<br>
> Stopped: [ p_zends_drbd:1 ]<br>
><br>
> And now DRBD situation on "old" Master node ( FRCVD2046 ):<br>
><br>
> service drbd status<br>
</div>> 0:zendsdata Unconfigured<br>
<br>
Right.<br>
Works "as designed".<br>
<div class="im"><br>
> Now if i run a DRBD service reload I have this scenario:<br>
><br>
> service drbd reload<br>
</div>> service drbd status<br>
<div class="im">> 0:zendsdata Connected Secondary/Primary UpToDate/UpToDate C<br>
<br>
</div>Of course.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
: Lars Ellenberg<br>
: LINBIT | Your Way to High Availability<br>
: DRBD/HA support and consulting <a href="http://www.linbit.com" target="_blank">http://www.linbit.com</a><br>
<br>
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br>
_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</font></span></blockquote></div><br></div>