Re: Pgsql resource agent of pacemaker
От | Shital A |
---|---|
Тема | Re: Pgsql resource agent of pacemaker |
Дата | |
Msg-id | CAMp7vw_3uwySE9t9C2dFwkDORjqesv9nTviFqU1x-Lsxd1_e5A@mail.gmail.com обсуждение исходный текст |
Ответ на | Pgsql resource agent of pacemaker (Shital A <brightuser2019@gmail.com>) |
Ответы |
Re: Pgsql resource agent of pacemaker
Re: Pgsql resource agent of pacemaker |
Список | pgsql-admin |
On Mon, 19 Aug 2019, 18:47 Shital A, <brightuser2019@gmail.com> wrote:
Hello,Need advise on below situation:Postgres 9.6Pacemaker 1.1.19Corosync 2.4.3We 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 understandThanks.
Any thoughts?
Thanks in advance!
В списке pgsql-admin по дате отправления: