[pgpool-general: 8313] Re: Problems with pcp_recovery_node

[Jon SCHEWE]

> > I used pg_ctl to take down psql-dev-01 and it showed a proper down state in the output of "show pool_nodes".
> > I then tried to bring it back online and got an error about the primary server not being able to be recovered.
> > However the primary server is psql-dev-03.
> > What am I missing here?
> >
> > Using pgpool 4.3.2 with postgresql 13.
> >
> > [jschewe-adm at psql-dev-01 ~]$ pcp_recovery_node -h psql.mgmt.bbn.com -p 9897 -U pgpool -n 0
> > Password:
> > ERROR:  process recovery request failed
> > DETAIL:  primary server cannot be recovered by online recovery.
> >
> > [jschewe-adm at psql-dev-01 ~]$ psql -h psql-dev.mgmt.bbn.com -p 9898 -U pgpool template1
> > Password for user pgpool:
> > psql (13.7)
> > SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off)
> > Type "help" for help.
> >
> > template1=> show pool_nodes;
> >  node_id |         hostname         | port | status | pg_status | lb_weight |  role   | pg_role | select_cnt | load_balance_node | replication_delay | replication_state | replication_sync_state | last_status_change 
> > ---------+--------------------------+------+--------+-----------+-----------+---------+---------+------------+-------------------+-------------------+-------------------+------------------------+---------------------
> >  0       | psql-dev-01.mgmt.bbn.com | 5432 | down   | down      | 0.333333  | standby | unknown | 0          | false             | 0                 |                   |                        | 2022-07-05 17:33:12
> >  1       | psql-dev-02.mgmt.bbn.com | 5432 | up     | up        | 0.333333  | standby | standby | 0          | false             | 0                 | streaming         | sync                   | 2022-07-01 16:37:19
> >  2       | psql-dev-03.mgmt.bbn.com | 5432 | up     | up        | 0.333333  | primary | primary | 6          | true              | 0                 |                   |                        | 2022-07-01 12:41:51
> > (3 rows)
> 
> Unfortunately pcp_recovery_node shows poor information when something
> goes wrong.  You should look into the primary PostgreSQL server's log
> to research an online recovery problem.

I tried the command again today and it worked. Perhaps there is some timing issue with how long after postgresql goes down before the recovery can happen.