Hello All, I am trying to compile a configuration for DRBD replication between two geographical sites, in order to achieve MySQL HA. According to my requirments, I only need one node at each site. The solution should be able to cope with split brain scenarios.
I was thinking about the following configuration: 1. Single node cluster at each site, with DRBD MS resource and a MySQL resource set with colocation to start on the DRBD master. 2. no-quorum-policy=ignore 3. stonith set to suicide 4. Boothd with a third site to run an arbitrator. DRBD and MySQL will depend on the ticket from Boothd using rsc_ticket ( loss-policy=demote). My questions are: 1. what are the cons of this configuration? Any caveats/pitfalls I am missing? will it work? 2. I haven't seen any concrete examples/configuration references on how to correctly configure pacemaker for single node cluster. Do I need corosync? can it be disabled? I've seen something about a "null comm module" but wasn't able to find any detailed information on how to configure it. Thank you in advance, Imri Zvik _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
