Sure, just add a colocation constraint for virtual_ip with proxy.
On 03/15/2017 05:06 AM, Frank Fiene wrote:
> Hi,
>
> Another beginner question:
>
> I have configured a virtual IP resource on two hosts and an apache resource
> cloned on both machines like this
>
> pcs resource create virtual_
Hallo Klaus,
Yes, indeed collocation was the culprit.
I've removed the constraint and replaced it with a collocation with the master.
#pcs constraint colocation add master drbd-demo-resource-clone with ClusterIP
INFINITY
And now it work like a charm, Master & Slave get started the nodes that h
Hi,
Another beginner question:
I have configured a virtual IP resource on two hosts and an apache resource
cloned on both machines like this
pcs resource create virtual_ip ocf:heartbeat:IPaddr2 params ip= op
monitor interval=10s
pcs resource create proxy lsb:apache2
statusurl="http://127.0.0.
Thank you all.
Done with csync2.
Frank
> Am 14.03.2017 um 01:33 schrieb Victor José Acosta DomÃnguez
> :
>
> You have many options to do that:
> - lsyncd+csync2/rsync
> - cron+rsync
> - glusterfs replicated f's
>
> Lsyncd + csync2 is a good option if you need near to real time replication
>
Hi!
I guess the collocation with ClusterIP is the culprit.
It leads to the clone not being started where ClusterIP
is not running.
Guess what you'd rather want is a collocation with
just the master-role of the clone.
Regards,
Klaus
On 03/14/2017 03:44 PM, Bruyninckx Kristof wrote:
>
> Hello,
>
>
Yesterday I found corosync took almost one hour to form a cluster(a
failed node came back online).
This for sure shouldn't happen (at least with default timeout settings).
So I captured some corosync packets, and opened the pcap file in wireshark.
But wireshark only displayed raw udp, no tot
Hello,
Currently I've tried to setup a 3 node asymmetric cluster, with the 3th node
only being used as a tie breaker.
monnod01 & monnod02 :
*centos 7.3
*pacemaker-1.1.15-11.el7_3.2.x86_64,
*corosync-2.4.0-4.el7.x86_64
*drbd84-utils-8.9.8-1.el7.elrepo.x86_64
*