[pgpool-general: 2408] Re: pgpool watchdog

[Sergey Arlashin]

It seems I solved this issue.
I should have used "heartbeat_destination0, heartbeat_destination_port0, wd_heartbeat_port" parameters. Once I used them everything got fine. 

Sorry for bothering :) 


--
Best regards,
Sergey Arlashin



On Jan 14, 2014, at 11:40 PM, Sergey Arlashin <sergeyarl.maillist at gmail.com> wrote:

> Hi!
> 
> I'm using pgpool 3.3.1 with pg backend with streaming replication.
> At the moment I'm trying to configure watchdog.
> 
> This is my watchdog configuration 
> 
> 
> pgpool node1:
> 
> use_watchdog                  = on
> delegate_IP                   = '192.168.33.200'
> wd_port                       = 9000
> 
> other_pgpool_hostname0        = '192.168.33.12'
> other_pgpool_port0            = 9999
> other_wd_port0                = 9000
> 
> wd_interval                   = 3
> 
> 
> 
> pgool node2:
> 
> use_watchdog                  = on
> delegate_IP                   = '192.168.33.200'
> wd_port                       = 9000
> 
> other_pgpool_hostname0        = '192.168.33.11'
> other_pgpool_port0            = 9999
> other_wd_port0                = 9000
> 
> wd_interval                   = 3
> 
> 
> When I restart pgpool on the active node IP 192.168.33.200 successfully moves to another node as expected. 
> But when I just power off the active node nothing happens. The second node doesn't become active. IP 192.168.33.200 doesn't move to the second node.
> 
> Is it a bug, or may be it is a misconfiguration issue? Or may be I misunderstand the idea of watchdog? 
> 
> --
> Best regards,
> Sergey Arlashin
> 
> 
>