Pgsql resource agent of pacemaker

From: Shital A <brightuser2019(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Pgsql resource agent of pacemaker
Date: 2019-08-19 13:17:06
Message-ID: CAMp7vw84=ydpzF-wMFvZkspuaRWAKQG29Uq==G09xhg29mPEWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

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.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Shital A 2019-08-19 18:06:56 Re: Pgsql resource agent of pacemaker
Previous Message Luca Ferrari 2019-08-18 07:17:19 Re: Error in Barman backup

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2019-08-19 14:07:30 Re: postmaster utilization
Previous Message John Donath 2019-08-19 12:19:54 RE: pg_basebackup exit codes