Re: what is causing different pcp_node_info status

From: Luca Ferrari <fluca1978(at)gmail(dot)com>
To: pgpool-general(at)lists(dot)postgresql(dot)org
Subject: Re: what is causing different pcp_node_info status
Date: 2025-10-23 06:04:50
Message-ID: CAKoxK+5+LFK4kk0Xay+9Rs8AYj9we0_M=T9md4HP0+rjZH6=uQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-general

On Fri, Oct 17, 2025 at 12:45 PM Luca Ferrari <fluca1978(at)gmail(dot)com> wrote:
> The problem is that the status of pg3 is not consistent: pg1 reports
> as "up up" while other nodes report as "down up".
> Please note that the updtae timestamp are in sync, 17:32:45 and hence
> the updated seems to have been propagated correctly within pgpool.
> Questions are:
> - is it safe right now to execute a pcp_attach_node ?
> - why is the status not consistent? Anything I should look for within the logs?

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?

Thanks,
Luca

In response to

Responses

Browse pgpool-general by date

  From Date Subject
Next Message VASUKI M 2025-10-23 07:13:04 Fwd: Automating Failover Resync & Re-Attach in pgpool2
Previous Message Sbob 2025-10-22 15:44:23 FDW/Foriegn Table pointing to pgpool never gets load balanced