> Master > / \ > Pre-Master Pre-Master > / | \ > Slave Slave Slave > > Master synchronizes its data with the attached Preferred Masters and Slaves > synchronizes its data from attached Prefered Master. > We want one of the Pre-Master to take over as master in case of master > instance failure (simultaneously tree restructuring is required) and one of > the slave to take over the Pre-Master role when one of the Pre-Master Fails.
So not only do the Pre-masters need to behave differently, the Slaves also need to know who the Pre-masters are. Is that correct? Yes, Slaves need to know which Pre-Master to connect. > So we have two probable options: > 1. An work around to achieve this tri-state efficiently without changing > pacemaker internals. > 2. Modify pacemaker to add this tri-state feature. > > So please suggest how to go about it. Thanks & Regards Shashi _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
