[pgpool-general: 5621] pgpool 3.6.4 failover - failover scenario question

[Shay Cohavi]

Hi,
I have 2 postgres servers (postgres 9.3.5) installed with pgpool(3.6.4) on
the same node.


server1 192.168.15.55
server 2 192.168.15.56
pgpool vip 192.168.15.59



​


# psql -U postgres -h 192.168.15.59 -p 9999 -c 'show pool_nodes'
 node_id |   hostname    | port | status | lb_weight |  role   | select_cnt
| load_balance_node | replication_delay
---------+---------------+------+--------+-----------+---------+------------+-------------------+-------------------
 0       | 192.168.15.55 | 5432 | up     | 0.500000  | primary | 3718
| true              | 0
 1       | 192.168.15.56 | 5432 | up     | 0.500000  | standby | 0
 | false             | 0



my question is about disaster recovery scenario:

1. *"primary postgres" and the "master pgpool" is on server1* . pgpool vip
established on this node (192.168.15.59)

2. server1 went down due to  power break. (server1 is dead!!!)

3. pgpool on server server2 get promoted (vip established 192.168.15.59) .

4. NO postgres failover action occurs by the pgpool. pgpool keeps searching
for primary postgres with no success.

should the new master pgpool execute an failover action(promote) to the
slave postgres ??



Thanks,
cohavisi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170714/8b97dbbe/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled drawing.jpg
Type: image/jpeg
Size: 41138 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170714/8b97dbbe/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool_conf_node2
Type: application/octet-stream
Size: 22126 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170714/8b97dbbe/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool_conf_node1
Type: application/octet-stream
Size: 22126 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170714/8b97dbbe/attachment-0003.obj>