[Linux-HA] Force switch with DRBD
Dominik Klein
dk at in-telegence.net
Tue Mar 4 02:38:52 MST 2008
DucaConte Balabam wrote:
> Hello,
> I've a cluster using heartbeat v2 and drbd in master/slave configuration.
>
> It's:
> ============
> Last updated: Tue Mar 4 09:49:30 2008
> Current DC: rman1c (875afc12-b88e-4940-9816-218d2a5911c3)
> 2 Nodes configured.
> 2 Resources configured.
> ============
>
> Node: rman1a (4d7bd4ec-c121-4b13-a2d4-aec820ea36d5): online
> Node: rman1c (875afc12-b88e-4940-9816-218d2a5911c3): online
>
> Master/Slave Set: ms-drbd0
> drbd0:0 (heartbeat::ocf:drbd): Master rman1a
> drbd0:1 (heartbeat::ocf:drbd): Started rman1c
> Resource Group: Oracle
> FS (heartbeat::ocf:Filesystem): Started rman1a
> V_IP (heartbeat::ocf:IPaddr2): Started rman1a
> Ora_DB (heartbeat::ocf:oracle): Started rman1a
> Ora_LSNR (heartbeat::ocf:oralsnr): Started rman1a
>
> How can I force all resources to move to the other node? There's acommand?
Try
crm_resource -M -r Oracle
This creates a rsc_location constraint, that does not allow "Oracle" to
run in its momentary location. Therefore, the cluster will migrate it.
Don't forget
crm_resource -U -r Oracle
afterwards to remove that rsc_location constraint (and allow the
resource to run on the first node again). If you do not do this, the
resource will never be able to run on the first node again.
Depending on your configuration, the resource might be migrated back to
the first node after the rsc_location constraint has been removed. If
so, you should read http://wiki.linux-ha.org/ScoreCalculation and set
resource_stickiness to a reasonable value.
Regards
Dominik
More information about the Linux-HA
mailing list