Re: Pgsql resource agent of pacemaker

Shital A <[email protected]> Mon, 19 Aug 2019 23:36:56 +0530

Newsgroups	gmane.comp.db.postgresql.admin,gmane.comp.db.postgresql.general
Message-ID	<CAMp7vw_3uwySE9t9C2dFwkDORjqesv9nTviFqU1x-Lsxd1_e5A@mail.gmail.com>

On Mon, 19 Aug 2019, 18:47 Shital A, <[email protected]> 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 streaming replication in async mode.
> Whenever there is a failover to standby, pgsql created a PGSQL.lock file
> in /var/lib/pgsql/tmp/ folder. We noticed that this file is created at
> random on any one of the nodes.
>
> Want to know:
> - Is there any logic behind which node it creates the lock file?
>
> - When a node in kept in HS:alone state ?
>
> - How can we check if failed node is at a log location behind current
> primary? So that we can force RA to start by deleting lock file?
>
> Please help to understand
>
> Thanks.
>
>
>
>
>
Any thoughts?

Thanks in advance!

>
>