Hi,
You can choose the default primary node for drbd by fixing constraints.
For exemple
<rsc_location id="drbd1_loc_nodeA" rsc="drbd1">
<rule id="pref_drbd1_loc_nodeA" score="600">
<expression attribute="#uname" operation="eq" value="nodeA"
id="pref_drbd1_loc_nodeA_attr"/>
</rule>
<rule id="pref_drbd1_loc_nodeB" score="800">
<expression attribute="#uname" operation="eq" value="nodeB"
id="pref_drbd1_loc_nodeB_attr"/>
</rule>
</rsc_location>
In this case, nodeB will be primary for resource drbd1. Is that what you
were looking for ?
Alan Robertson a écrit :
Doug Knight wrote:
Hi Alan,
This example helps, but there's one thing I can't seem to grasp. I
understand how these rules make sure that the file system stays on the
same node as the primary drbd, but what determines which node the
primary drbd is on? With a mirrored partition from drbd, I really don't
care which node takes over as master, but I need one of them to do it.
Right now it comes up as two slaves, waiting for one or the other to ask
to be promoted. I was hoping someone out there had a complete cib.xml
file configuring drbd with something else (i.e. database, apache, IP
address, etc), but I've gotten no response on that (other than your
example :)
This should be handled by the DRBD resource agent.
Have you ever synced up the two sides in DRBD?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
