Hello,
I have a three node pacemaker cluster running using the Master Slave
primitive. Its an asymmetric cluster with one node running as master and
the other one as slave, the third one serving as a quoram node.
Our DC has frequent network issues. One thing, in particular, is the master
partitio
corosync v2.
>
> digimer
>
> On 13/04/17 06:18 PM, neeraj ch wrote:
> > I have dreaded that answer. Maybe I can fix vote quorum on corosync 1.4.
> > Or maybe I can get 2.X working on EL6. Really don't wanna deal with
> > another layer.
> >
> >
I have dreaded that answer. Maybe I can fix vote quorum on corosync 1.4. Or
maybe I can get 2.X working on EL6. Really don't wanna deal with another
layer.
Thanks.
On Thu, Apr 13, 2017 at 2:10 PM, Digimer wrote:
> On 13/04/17 05:07 PM, neeraj ch wrote:
> > Hi,
> >
&
Hi,
I have three node cluster set up. My corosync config is as follows.
compatibility: whitetank
totem {
version: 2
secauth: on
threads: 0
interface {
member{
memberaddr: ip
}
member{
memberaddr:ip
}
member{
memberaddr:ip
I am running it on centos 6.6. I am killing the "pacemakerd" process using
kill -9.
hmm, stonith is used for detection as well? I thought it was used to
disable malfunctioning nodes.
On Fri, Apr 7, 2017 at 7:58 AM, Ken Gaillot wrote:
> On 04/05/2017 05:16 PM, neeraj ch wrote:
Hello All,
I noticed something on our pacemaker test cluster. The cluster is
configured to manage an underlying database using master slave primitive.
I ran a kill on the pacemaker process, all the other nodes kept showing the
node online. I went on to kill the underlying database on the same nod
ic IP rather than the private IP ? Would it
be any better if I used corosync 2.X , for the same setup ?
On Thu, Oct 13, 2016 at 12:41 AM, Klaus Wenninger
wrote:
> On 10/13/2016 09:30 AM, Jan Friesse wrote:
> > neeraj ch napsal(a):
> >> Hello ,
> >>
> >> We are testi
Hello ,
We are testing out corosync and pacemaker for DB high availability on the
cloud. I was able to set up a cluster with in a DC using corosync 1.4 and
pacemaker 1.12. It works great and I wanted to try a cross DC cluster. I
was using unicast as multicast was disabled by default.
I was not su
Hello,
I have pacemaker cluster running on Amazon Linux 2013.03 , details as
follows.
OS : Amazon Linux 2013.03 64 bit (based off on el6)
Pacemaker version : 1.1.12 downloaded form
http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/CentOS_CentOS-6/
I downloaded all of pacem
