too many clients already“ in my browser. In seeing this, I realized how common it is to underestimate the connection count while we are busy configuring
no such file or directory: container process not found Normal Pulled 174m (x5 over 4h25m) kubelet Container image "docker.io/bitnami/pgpool:4.2.2-debian-10-r70" already present on machine Warning Unhealthy 163m kubelet Liveness probe failed: pgpool 0.0.0.0 INFO ==> Checking pgpool health.....
If I'm reading this correctly, users can get connection from Vert.x PgPool which is already closed. @pjgg say it's a bug, because end users should get valid connections only @tsegismont says it's a known limitation because some parts are missing on Vert.x side the limitation has been ...
reserved_connections (integer) When this parameter is set to 1 or greater, incoming connections from clients are not accepted with error message "Sorry, too many clients already", rather than blocked if the number of current connections from clients is more than (num_init_children - reserved_...
In the case When clients already connect to Pgpool-II and PostgreSQL is shutdown (please note that if no client connects to Pgpool-II at all, shutting down of PostgreSQL does not trigger a failover). If failover_command is configured and a failover happens, failover_command gets executed....