-
Notifications
You must be signed in to change notification settings - Fork 1k
pg: cannot set transaction read write mode during recovery #2354
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
Comments
same problem |
Observed the exact same issue more than once on an instance, resolves if the read replica is restarted |
same problem |
same issue |
same here |
Still reproducible on latest operator v1.12.2. |
Same problem |
1 similar comment
Same problem |
@lkgGitHub I am facing the same issue when we try to write to Aurora Postgres secondary region's reader endpoint. We have write forwarding enabled, so ideally the write operation should have succeeded. Did you manage to solve the problem? |
I have two pod in kubernetes, postgres-service-0 and postgres-service-1. First postgres-service-1 is master.
After PostgreSQL master-slave failover, Application client connection PostgreSQL error:"pg: cannot set transaction read write mode during recovery".
But PostgreSQL pods are all running.
When I restart the application, it can be restored.
Which image of the operator are you using?
registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
spilo-14:2.1-p7
Where do you run it - cloud or metal? Kubernetes or OpenShift?
Kubernetes
Are you running Postgres Operator in production? [yes | no]
yes
postgres-service-1
postgres-service-0 log:
Some general remarks when posting a bug report:
The text was updated successfully, but these errors were encountered: