public inbox for [email protected]  

help / color / mirror / Atom feed

From: Luca Ferrari <[email protected]>
To: [email protected]
Subject: Re: what is causing different pcp_node_info status
Date: Thu, 23 Oct 2025 08:04:50 +0200
Message-ID: <CAKoxK+5+LFK4kk0Xay+9Rs8AYj9we0_M=T9md4HP0+rjZH6=uQ@mail.gmail.com> (raw)
In-Reply-To: <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com>
References: <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com>

On Fri, Oct 17, 2025 at 12:45 PM Luca Ferrari <[email protected]> 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

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]
  Subject: Re: what is causing different pcp_node_info status
  In-Reply-To: <CAKoxK+5+LFK4kk0Xay+9Rs8AYj9we0_M=T9md4HP0+rjZH6=uQ@mail.gmail.com>

* 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