public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tatsuo Ishii <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: what is causing different pcp_node_info status
Date: Tue, 04 Nov 2025 10:36:53 +0900 (JST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKoxK+5D4szPoPOWvg6aaJLWEKDf5sHQFgNOCJrod+swKJWCSA@mail.gmail.com>
References: <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com>
	<CAKoxK+5+LFK4kk0Xay+9Rs8AYj9we0_M=T9md4HP0+rjZH6=uQ@mail.gmail.com>
	<CAKoxK+5D4szPoPOWvg6aaJLWEKDf5sHQFgNOCJrod+swKJWCSA@mail.gmail.com>

> On Thu, Oct 23, 2025 at 8:04 AM Luca Ferrari <[email protected]> wrote:
>>
>> I am still observing the issue, the best situation I come is all nodes
>> reported as "up up" when queryed on pg1 (primary) and "waiting up"
>> when queried from pg2 and pg3.
>> could it be network latency or a similar issue?
> 
> As explained clearly here
> <https://github.com/pgpool/pgpool2/issues/131#issuecomment-3436197043;
> the information about the nodes is collected and kept in shared
> memory.
> Is there any chance the same process is applied to the pgpool node status?
> I observed that even a machine reboot does not seem to make pgpool
> report a status better than "waiting up", evne after minutes, and
> while replicas are streaming.
> Restarting then the pgpool service brings the status "up up", this
> makes me think there is something blocking or delaying pgpool to
> collect data, and when the service is restarted the node is forced to
> "dig" the other node status.
> Something I could investigate on?

You are misunderstanding what "waiting" means. It means "Node is
up. No connections yet." [1] If you are only interested in the node is up
or down, you can safely assume that "waiting" == "up".

Best regards,
[1] https://www.pgpool.net/docs/latest/en/html/pcp-node-info.html
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: what is causing different pcp_node_info status
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox