On Thu, 31 Jan 2013 08:12:29 -0700 Greg Woods <[email protected]> wrote: > On Thu, 2013-01-31 at 02:09 +0000, Robinson, Eric wrote: > > > the secondary should wait for a manual command to become primary. > > That can be accomplished with the "meatware" STONITH device. Requires > a command to be run to tell the wannabe primary that the secondary is > really dead (and, of course, you had better be sure that the secondary > is really dead before the command is run to avoid split brain). > > > > > > 2. The secondary should refuse to become primary even if manually > > ordered to do so if it cannot communcate with DataCenterC. > > I don't know any way to do that exactly, but you might be able to use > order constraints to require some sort of ping-based resource to be > successfully started before the other resources can start.
I like to run the ping-resource on all nodes and make a certain ping-threshold a prerequisite for VMs and similar services. The weight on that location rule can then determine whether machines are also stopped/moved if the node looses ping. Which in your case would be that your cluster shuts down when DataCenterC goes down. What I didn't yet find was some kind of a suicide-method for nodes to just reset and restart in standby/looking for the cluster when something strange happens. Like loosing all of the (currently four) links on the network devices... Have fun, Arnold
signature.asc
Description: PGP signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
