On Tue, 24 Sep 2019, 22:20 Shital A, wrote:
> Hello,
>
> We have setup active-passive cluster using streaming replication on
> Rhel7.5. We are testing pacemaker for automated failover.
> We are seeing below issues with the setup :
>
> 1. When a failover is triggered when d
Hello,
We have setup active-passive cluster using streaming replication on
Rhel7.5. We are testing pacemaker for automated failover.
We are seeing below issues with the setup :
1. When a failover is triggered when data is being added to the primary by
killing primary (killall -9 postgres), the st
On Tue, 20 Aug 2019, 09:29 Shital A, wrote:
>
>
> Hello,
>
> Need advise on below situation:
>
> Postgres 9.6
> Pacemaker 1.1.19
> Corosync 2.4.3
>
> We are testing HA setup on a two node cluster using pacemaker, corosync
> stack. The replication is
Hello,
Need advise on below situation:
Postgres 9.6
Pacemaker 1.1.19
Corosync 2.4.3
We are testing HA setup on a two node cluster using pacemaker, corosync
stack. The replication is streaming replication in async mode.
Whenever there is a failover to standby, pgsql created a PGSQL.lock file in
/
Hello,
Postgres version : 9.6
OS:Rhel 7.6
We are working on HA setup for postgres cluster of two nodes in
active-passive mode.
Installed:
Pacemaker 1.1.19
Corosync 2.4.3
The pacemaker agent with this installation doesn't support automatic
failback. What I mean by that is explained below:
1. Clu
