[Pacemaker] Mysqlping resource for Mysql Master-Master replication

Viacheslav Biriukov v.v.biriukov at gmail.com
Mon Nov 14 10:40:34 EST 2011


Can I manage cloned resource separatelyю For example restart cloned Mysql
server on the first ndoe. But don't touch it on the second? It's no clear
for me from the documentation.

2011/11/14 Andrew Beekhof <andrew at beekhof.net>

> On Mon, Nov 7, 2011 at 4:54 AM, Viacheslav Biriukov
> <v.v.biriukov at gmail.com> wrote:
> > Hi.
> > Yes it is useful in master-master replication for Mysql HA.
> > How do you see dependency handling in this situation? We want to start
> Mysql
> > server on both nodes. So we nee to use clone resorce, right? But in this
> > case we can't use nether collocation nether group or location tags.
>
> You can colocate a group with a clone and tell the clone to prefer
> certain nodes with location constraints.
> What made you think otherwise?
>
> > And mysqlping resource do monitoring and with location tag do good job
> for
> > us.
> >
> >
> > 2011/10/19 Raoul Bhatia [IPAX] <r.bhatia at ipax.at>
> >>
> >> On 2011-06-12 23:10, Viacheslav Biriukov wrote:
> >>>
> >>> We have the situation when our  mysql  server hangs. So it begins to
> >>> restart. But it takes a while. So we need fast switching for the other
> >>> mysql master node.
> >>
> >> hi!
> >>
> >> do i correctly understand that this is only beneficial in a master-
> >> master setup? and/or why is the regular monitoring and dependency
> >> handling not enough?
> >>
> >> thanks,
> >> raoul
> >> --
> >> ____________________________________________________________________
> >> DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia at ipax.at
> >> Technischer Leiter
> >>
> >> IPAX - Aloy Bhatia Hava OEG         web.          http://www.ipax.at
> >> Barawitzkagasse 10/2/2/11           email.            office at ipax.at
> >> 1190 Wien                           tel.               +43 1 3670030
> >> FN 277995t HG Wien                  fax.            +43 1 3670030 15
> >> ____________________________________________________________________
> >>
> >> _______________________________________________
> >> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >
> >
> >
> > --
> > Viacheslav Biriukov
> > BR
> > http://biriukov.com
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >
> >
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>



-- 
Viacheslav Biriukov
BR
http://biriukov.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111114/5cc73aa2/attachment-0003.html>


More information about the Pacemaker mailing list