[ClusterLabs] [ClusterLabs Developers] pacemaker geo redundancy - 2 nodes
Ken Gaillot
kgaillot at redhat.com
Tue Jul 23 09:41:07 EDT 2019
Hi Rohit,
Did you see the two earlier replies?
https://lists.clusterlabs.org/pipermail/users/2019-July/026035.html
On Tue, 2019-07-23 at 11:14 +0530, Rohit Saini wrote:
> Gentle Reminder!!
>
> On Wed, Jul 17, 2019 at 1:14 PM Rohit Saini <
> rohitsaini111.forum at gmail.com> wrote:
> > Gentle Reminder!!
> >
> > On Mon, Jul 15, 2019 at 12:10 PM Rohit Saini <
> > rohitsaini111.forum at gmail.com> wrote:
> > > Hi All,
> > >
> > > I know pacemaker booth is being used for geographical redundancy.
> > > Currently I am using pacemaker/corosync for my local two-node
> > > redundancy.
> > > As I understand, booth needs atleast 3 nodes to work correctly to
> > > do the automatic failovers. So it does not fit my requirements.
> > >
> > > Few queries are
> > > 1) Can I make use of my current pacemaker/corosync to make it
> > > work across my two geographical nodes for automatic failovers,
> > > considering I am ready to ignore split-brain scenarios. I may
> > > need to tweak some timers I believe. Is this approach possible?
> > > 2) Any disadvantages of going this way?
> > >
> > >
> > > Thanks,
> > > Rohit
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot <kgaillot at redhat.com>
More information about the Users
mailing list