[pgpool-general: 3557] Re: Upgrade from 3.3.1 to 3.3.3

[Tatsuo Ishii]

> Hey All,
> 
> We have upgraded PGPool node to 3.3.3 (from 3.3.1) and tested, but we are
> hitting an error.
> 
> PSQL access through the node hangs after an amount of time (as low as 40
> minutes, the highest overnight). Has anyone struck this before?

Something similar to this?
http://www.pgpool.net/mantisbt/view.php?id=107

If so, it has been fixed in 3.3.4.

> We had debug mode turned on, but the logs do not seem to show any errors
> except for those shown below. These errors appear to have been happening
> when PSQL access was working.
> 
> 2015-03-20 08:24:47 DEBUG: pid 17173: health check: clearing alarm
> 2015-03-20 08:24:48 LOG:   pid 17207: send_failback_request: fail back 0 th
> node request from pid 17207
> 2015-03-20 08:24:48 DEBUG: pid 17173: failover_handler called
> 2015-03-20 08:24:48 DEBUG: pid 17173: failover_handler: starting to select
> new master node
> 2015-03-20 08:24:48 ERROR: pid 17173: failover_handler: invalid node_id 0
> status:2 MAX_NUM_BACKENDS: 128

This happens if pcp_attach_node is executed against live node (in this
case 0) and should be harmless. Did you do it?

> While I can't access the backend servers through PSQL PCP commands are
> still responsive.
> 
> [root at ppcdat-devr204 tmp]# pcp_node_info 1 ppcdat-devr204 9898 postgres
> postgres 1
> 10.51.10.173 5432 2 0.500000
> 
> [root at ppcdat-devr204 tmp]# pcp_node_info 1 ppcdat-devr204 9898 postgres
> postgres 0
> 10.51.9.174 5432 2 0.500000
> 
> 
> Cheers,
> 
> 
> James Sewell,
> PostgreSQL Team Lead / Solutions Architect
> ______________________________________
> 
> 
>  Level 2, 50 Queen St, Melbourne VIC 3000
> 
> *P *(+61) 3 8370 8000  *W* www.lisasoft.com  *F *(+61) 3 8370 8099
> 
> -- 
> 
> 
> ------------------------------
> The contents of this email are confidential and may be subject to legal or 
> professional privilege and copyright. No representation is made that this 
> email is free of viruses or other defects. If you have received this 
> communication in error, you may not copy or distribute any part of it or 
> otherwise disclose its contents to anyone. Please advise the sender of your 
> incorrect receipt of this correspondence.