View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000759 | pgpoolAdmin | Bug | public | 2022-06-28 16:31 | 2022-06-30 14:44 |
| Reporter | arihant.joshi@infoworks.io | Assigned To | |||
| Priority | normal | Severity | block | Reproducibility | sometimes |
| Status | closed | Resolution | open | ||
| Product Version | 4.2.0 | ||||
| Summary | 0000759: pcp_attach_node gives a successful output, however fails to actually attach | ||||
| Description | PGPool Version-4.2.6, Postgres Version-13.7 This is a fully HA Kubernetes Environment - 2 postgres and 2 pgpool pods. After letting this environment run for a while, we notice the failover in the postgres standby. I have no name!@pgpool-postgresql-ha-pgpool-0:/$ pcp_node_info -h localhost -p 9898 -U admin -n 1 Password: pgpool-postgresql-db-1.postgresql-db-headless.pgpool.svc.cluster.local 5432 3 0.500000 down standby 31227816 2022-06-28 07:24:52 To re-attach I have no name!@pgpool-postgresql-ha-pgpool-0:/$ pcp_attach_node -h localhost -p 9898 -U admin -n 1 Password: pcp_attach_node -- Command Successful However, its still detached I have no name!@pgpool-postgresql-ha-pgpool-0:/$ pcp_node_info -h localhost -p 9898 -U admin -n 1 Password: pgpool-postgresql-db-1.postgresql-db-headless.pgpool.svc.cluster.local 5432 3 0.500000 down standby 31250560 2022-06-28 07:26:10 This is a blocker issue for us adapting the HA setup for postgres. Additional Note: The given pgpool pod is the leader- The postgres pods are reachable using the given host values- I have no name!@pgpool-postgresql-ha-pgpool-0:/$ pcp_watchdog_info -h localhost -p 9898 -U admin Password: 2 YES pgpool-postgresql-ha-pgpool-0.postgresql.pgpool.svc.cluster.local:5432 Linux pgpool-postgresql-ha-pgpool-0 pgpool-postgresql-ha-pgpool-0.postgresql.pgpool.svc.cluster.local pgpool-postgresql-ha-pgpool-0.postgresql.pgpool.svc.cluster.local:5432 Linux pgpool-postgresql-ha-pgpool-0 pgpool-postgresql-ha-pgpool-0.postgresql.pgpool.svc.cluster.local 5432 9000 4 LEADER pgpool-postgresql-ha-pgpool-1.postgresql.pgpool.svc.cluster.local:5432 Linux pgpool-postgresql-ha-pgpool-1 pgpool-postgresql-ha-pgpool-1.postgresql.pgpool.svc.cluster.local 5432 9000 7 STANDBY Also, both pods are reachable using the given DNS I have no name!@pgpool-postgresql-ha-pgpool-0:/$ curl http://pgpool-postgresql-db-1.postgresql-db-headless.pgpool.svc.cluster.local:5432 curl: (52) Empty reply from server I have no name!@pgpool-postgresql-ha-pgpool-0:/$ curl http://pgpool-postgresql-db-0.postgresql-db-headless.pgpool.svc.cluster.local:5432 curl: (52) Empty reply from server | ||||
| Steps To Reproduce | This issue is seen intermittently. | ||||
| Tags | No tags attached. | ||||
|
|
Because it isn't a pgpoolAdmin issue, could you close this issue and open a new issue with "Project:Pgpool-II"? When you open a issue, please select project "Pgpool-II". |
|
|
@pengbo I wish I could, but I'm not seeing any buttons/menus that would let me close/delete/archive this issue. I think on mantisBT you can disable "close" issue even from the reporter. Can an admin close this? https://mantisbt.org/forums/viewtopic.php?t=23955 |
|
|
Sure. Close issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-06-28 16:31 | arihant.joshi@infoworks.io | New Issue | |
| 2022-06-30 11:55 | pengbo | Note Added: 0004087 | |
| 2022-06-30 14:25 | arihant.joshi@infoworks.io | Note Added: 0004088 | |
| 2022-06-30 14:44 | pengbo | Status | new => closed |
| 2022-06-30 14:44 | pengbo | Note Added: 0004089 |
