[pgpool-general: 9416] Re: FATAL: failed to read kind from backend
Ron Johnson
ronljohnsonjr at gmail.com
Fri Mar 28 13:51:14 JST 2025
On Fri, Mar 28, 2025 at 12:27 AM Tatsuo Ishii <ishii at postgresql.org> wrote:
> > On Thu, Mar 27, 2025 at 8:19 PM Tatsuo Ishii <ishii at postgresql.org>
> wrote:
> >
> >> > On Thu, Mar 27, 2025 at 9:28 AM Tatsuo Ishii <ishii at postgresql.org>
> >> wrote:
> >> >
> >> >> > Last week, I disabled load balancing, but the replica still has
> some
> >> >> weight
> >> >> > Might that be causing the problem?
> >> >> > load_balance_mode = off
> >> >> > backend_weight0 = 2
> >> >> > backend_weight1 = 1
> >> >>
> >> >> No, I don't think so. If load_balance_mode = off, then backend_weight
> >> >> is ignored.
> >> >
> >> >
> >> > I'm still getting the WARNING and FATAL messages even after stopping
> >> pgpool
> >> > on all three nodes, but only starting pgpool on nodes C and A.
> >>
> >> The error (kind mismatch) is nothing related to watchdog.
> >>
> >
> > OK. But what _is_ causing the FATAL "kind mismatch" errors?
>
> Under investigation. I am failing to reproduce the problem.
>
Thank you.
The error _seems_ to be volume-related: happens more when the system is
busy. (But maybe a busy system has more opportunity to trigger the bug.
Would it help if I cranked up log_min_messages to DEBUG1 or even DEBUG2?
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20250328/ddc19df2/attachment.htm>
More information about the pgpool-general
mailing list