Hi Lars,<div><br></div><div>yes now is more clar for me.</div><div><br></div><div>We made "node standby" to simulate a package switching ( in a wrong way it seems ).</div><div>Let me ask one thing: do ypu know a way to do a "cluster functionalty" test?</div>
<div><br></div><div>I'm thinking about unplugging lan cable... is that a right test?</div><div><br></div><div>Thanks again for your support.</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 Tue, Feb 26, 2013 at 10:31:27AM +0100, Simone Del Pinto wrote:<br>
> Thank u lars!<br>
><br>
> I've implemented a cron scripts that if found drbd in Unconfigured state do<br>
> a service reload. With this workaruond all seems to work fine.<br>
<br>
</div>Then you don't understand your cluster manager at all.<br>
Get rid of this cron job as soon as possible.<br>
See below.<br>
<div class="im"><br>
> But... if the service really switch on other node and, for a reason, it<br>
> come back to last nod what happen?<br>
><br>
> It is very strange... it need a manual restart however.<br>
<br>
</div>I don't really understand your question.<br>
<br>
But if you want some node to be able to take over,<br>
you must not set it "standby".<br>
<br>
Maybe some misundernstanding on the concept of "node standby" in pacemaker?<br>
<br>
In pacemaker you switch a node to "standby" to take it down for maintenance.<br>
<br>
In normal operation of the cluster, all nodes must be *online*.<br>
Some of the online nodes run resources, some run other resources,<br>
some run instances of clones of the same resource,<br>
some run instances of multi-state resources as Master or Slave.<br>
<br>
The node state "standby" in the Pacemaker sense is one that does not<br>
really take part in clustering anymore, possibly because it is about<br>
to be taken down for maintenance/hardware upgrade/whatever.<br>
<br>
What you apparently think of "standby" would be a node waiting to take<br>
over. For that to happen, it must be "online" in the pacemaker sense,<br>
just not running the resources in question yet (but probably the Slave<br>
instances of the DRBDs).<br>
<br>
Hope that clears things up a bit.<br>
<br>
Lars<br>
<div><div class="h5"><br>
><br>
> Simone<br>
><br>
> 2013/2/26 Lars Ellenberg <<a href="mailto:lars.ellenberg@linbit.com">lars.ellenberg@linbit.com</a>><br>
><br>
> > 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<br>
> > MySQL server.<br>
> > ><br>
> > > corosync and pacemaker ensure that we have a virtuel IP running and that<br>
> > 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<br>
> > standy<br>
> > > ( crm node standby )<br>
> ><br>
> > "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>
> ><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>
> > > 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>
> > > 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>
> > > 0:zendsdata Unconfigured<br>
> ><br>
> > Right.<br>
> > Works "as designed".<br>
> ><br>
> > > Now if i run a DRBD service reload I have this scenario:<br>
> > ><br>
> > > service drbd reload<br>
> > > service drbd status<br>
> > > 0:zendsdata Connected Secondary/Primary UpToDate/UpToDate C<br>
> ><br>
> > Of course.<br>
> ><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>
> ><br>
<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>
<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>
</div></div>please don't Cc me, but send to list -- I'm subscribed<br>
</blockquote></div><br></div>