No,  that is not what he (Jared) is asking.  His configuration is not failing 
over.   One thing that you should not be doing is placing the primary into 
(StandAlone) at the DRBD level unless you are trying to test the device 
pass-thru function,  even then I don't believe that is the proper way to test.  
  You really need to verify your configuration (both Heartbeat and DRBD) all 
four files (ha.cf, haresources,global_common.conf and *.res).  Somewhere there 
is a mistake.  If properly configured, servicing down Heartbeat, or halting 
and/or rebooting the currently primary should force the secondary to become the 
primary node within the time period specified in "ha.cf".


That is all I know,  yes it is not much but it seems to be enough since my 
configuration works.  

James

----- Original Message -----
From: Felix Frank [mailto:[email protected]]
Sent: Wednesday, April 03, 2013 04:03 AM
To: Jared Harvey <[email protected]>
Cc: drbd-user <[email protected]>
Subject: Re: [DRBD-user] Problem with Failover with DRBD, Heartbeat,    and 
Pacemaker

Hi,

On 04/02/2013 09:31 PM, Jared Harvey wrote:
> The problem arises when I put the primary node to standby.  The same
> thing happens when I reboot, power off, or pull the plug.

it actually works as designed.

> /Master/Slave Set: ms_g_drbd/
> 
> /     Slaves: [ hpsata02 ]/
> 
> /     Stopped: [ g_drbd:0 ]/
> 
> / /
> 
> On node 2 this is the DRBD status
> 
>  
> 
> /root@HPSATA02:~# service drbd status/
> 
> /drbd driver loaded OK; device status:/
> 
> /version: 8.3.7 (api:88/proto:86-91)/
> 
> /srcversion: EE47D8BF18AC166BE219757/
> 
> /m:res   cs            ro                 ds                 p  mounted 
> fstype/
> 
> /0:meta  WFConnection  Secondary/Unknown  Outdated/DUnknown  C/
> 
> /1:data  WFConnection  Secondary/Unknown  Outdated/DUnknown  C/
> 

DRBD is fully disabled on the standby/offline node, because setting a
node to standby means "migrate all HA services away and stop them locally".

In the DRBD case, this is not really what anybody wants (because your
cluster enters a degraded state), but there is no workaround that I know of.

Avoid the use of standby outside of actual maintenance periods.

HTH,
Felix
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Reply via email to