[pgpool-general: 3151] PGPool hang

[James Sewell]

Hey All,

I am getting some strange behaviour with some PGPool instances in AWS.

I have 2 x PGPool instances (watchdog on) and 2 x PostgreSQL instances. I
am using PostgreSQL replication with an external cluster solution.

I have the following nodes:

show pool_nodes;
 node_id |  hostname   | port | status | lb_weight |  role
---------+-------------+------+--------+-----------+---------
 0       | 10.51.9.227 | 5432 | 2      | 0.500000  | standby
 1       | 10.51.10.29 | 5432 | 2      | 0.500000  | primary
(2 rows)


The following appears in my log files, after which PGPool effectively hangs
on both nodes. A restart of PGpool on both nodes fixes the problem.

2014-09-04 13:37:41 LOG:   pid 24322: wd_send_response:
WD_STAND_FOR_LOCK_HOLDER received it
2014-09-04 13:37:41 LOG:   pid 24322: degenerate_backend_set: 1 fail over
request from pid 24322
2014-09-04 13:37:41 LOG:   pid 24311: wd_start_interlock: start interlocking
2014-09-04 13:37:41 LOG:   pid 24311: starting degeneration. shutdown host
10.51.10.29(5432)
2014-09-04 13:37:41 ERROR: pid 24311: failover_handler: no valid DB node
found
2014-09-04 13:37:41 LOG:   pid 24311: Restart all children
2014-09-04 13:37:42 LOG:   pid 24311: find_primary_node_repeatedly: waiting
for finding a primary node

Any ideas? As this in AWS I wouldn't be surprised if a network issue caused
the primary to disappear briefly - but it is never found again.

I am trying to recreate but haven't had luck yet.

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140909/6b4abbe0/attachment.html>