Quoting Jaap Winius :
Very interesting. I'm already running DRBD 9, so that base has
already been covered, but here's some extra information: My test
system actually consists of a single 4-node DRBD cluster that spans
two data centers, with each data center having a 2-node Pacemaker
On February 26, 2020 2:36:46 PM GMT+02:00, "Nickle, Richard"
wrote:
>I spent many, many hours tackling the two-node problem and I had
>exactly
>the same symptoms (only able to get the resource to move if I moved it
>manually) until I did the following:
>
>* Switch to DRBD 9 (added LINBIT repo
Quoting "Nickle, Richard" :
* Switch to DRBD 9 ...
* Build a third diskless quorum arbitration node.
Very interesting. I'm already running DRBD 9, so that base has already
been covered, but here's some extra information: My test system
actually consists of a single 4-node DRBD cluster
I spent many, many hours tackling the two-node problem and I had exactly
the same symptoms (only able to get the resource to move if I moved it
manually) until I did the following:
* Switch to DRBD 9 (added LINBIT repo because DRBD 8 is the default in the
Ubuntu repo)
* Build a third diskless
Hi folks,
My 2-node test system has a DRBD resource that is configured as follows:
~# pcs resource defaults resource-stickiness=100 ; \
pcs resource create drbd ocf:linbit:drbd drbd_resource=r0 \
op monitor interval=60s ; \
pcs resource master drbd master-max=1 master-node-max=1
