[pgpool-general: 8658] Re: recovery failed to start in 0 second

[Todd Stein]

Thank you.



Regards,

Todd Stein

-----Original Message-----
From: Bo Peng <pengbo at sraoss.co.jp> 
Sent: Monday, March 20, 2023 8:04 AM
To: Todd Stein <todd.stein at microfocus.com>
Cc: pgpool-general at pgpool.net
Subject: Re: [pgpool-general: 8651] recovery failed to start in 0 second

Hello,

> I sometimes get the following message when trying to recover a down cluster node:
> 
> pcp_recovery_node -h 10.78.121.1 -p 9898 -U pgpool -n 0
> Password:
> ERROR:  recovery is checking if postmaster is started
> DETAIL:  postmaster on hostname:"catvmtspg02a.domain.net" 
> database:"template1" user:"postgres" failed to start in 0 second
> 
> How can I stop this from happening?  The pcp_recovery_node process is usually successful on a later attempt.

After running remote start of the target node, Pgpool-II will try to connect to the PostgreSQL node to check if postmaster is started.

First, Pgpool-II will try to connect to database "postgres" 3 times.
If it fails, Pgpool-II will try to connect to "template1" periodically within recovery_timeout/3 seconds.

It seems you have configured recovery_timeout = 0 and 0 means no wait.

If the startup of PostgreSQL takes time, please increase recovery_timeout.

--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS LLC
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sraoss.co.jp%2F&data=05%7C01%7Ctodd.stein%40microfocus.com%7C2954b8108fd742f733d008db293b22e9%7C856b813c16e549a585ec6f081e13b527%7C0%7C0%7C638149106147553623%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tMNlTik5dlHL3HLsoAEbfTIim%2BLFogwPl6MdmPlPQ7g%3D&reserved=0