-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/postgresql-ha] “kind does not match between main” errors in Postgres-HA (bitnami) + Pgpool setup #31697
Labels
postgresql-ha
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
Comments
Forgot to include my config as it stands now.
|
Hi! Thank you for opening the ticket. I see this is a duplicate of #4785. Let's continue the conversation there. Please check what we did to reproduce the issue and please provide us with exact steps that trigger the issue, as we were having problems reproducing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
postgresql-ha
solved
tech-issues
The user has a technical issue about an application
triage
Triage is needed
Name and Version
bitnami/postgres-ha
What architecture are you using?
amd64
What steps will reproduce the bug?
Issue Description
I am running the Helm chart to deploy a Postgres HA cluster with Pgpool. Everything appears to work initially, but I often see this error in the logs (or from the client):
I’m unsure whether it’s an actual data out-of-sync problem or a separate issue (e.g., a conflict in the protocol, some mismatch in replication, etc.). But this error recurs under normal operation - even with the default helm setup.
Steps to Reproduce
Deploy the Helm chart.
Connect to the cluster via Pgpool or a client like psql/pgAdmin.
Perform writes, reads, or schema modifications (for example, creating and dropping tables).
Observe the logs from Pgpool/PostgreSQL pods. The error appears as:
kind does not match between main ...
What I Have Tried
Changing Pgpool settings for failover:
failover_on_backend_error = on/off
failover_on_backend_shutdown = on/off
Checking replication status via pg_stat_replication in the primary node (everything appears normal).
Ensuring the version of pgpool images and postgresql-repmgr images match or are compatible.
Despite these attempts, the error persists. I don’t see obvious replication problems (no huge replication lag). Even with not replication lag - often I’ll see logs that a database doesn’t exist even though it shows when listing databases. However, the error’s presence is concerning, and I want to ensure there isn’t a hidden replication or configuration mismatch.
Questions / Requests for the Community
Has anyone encountered this specific “kind does not match between main” error in a Bitnami Postgres-HA + Pgpool setup and actually overcame it ?
Does this chart actually work for anybody in production and if so, could you post your values.yaml so i could compare the differences?
Are you using any custom parameters or values?
No response
What is the expected behavior?
No response
What do you see instead?
It fails
Additional information
No response
The text was updated successfully, but these errors were encountered: