[pgpool-general: 2812] Re: pgpool 3.3 and watchdog
joar.jegleim at gmail.com
Thu May 8 16:10:14 JST 2014
Please forgive me, false alarm, it works now.
When I was reproducing this to send you the logs it suddenly worked (?) .
I suspect it's because I've disabled iptables since I was working with
this last time.
I've previously opened up heartbeat port 9694 and watchdog port 9000
between the 2 nodes (+ pgpool and postgres ports of course), I thought
mabye that was enough .
Mabye I will have to open up for the delegate ip as well, or mabye
there are some more ports I will have to open up.
Anyway, I will continue testing with no iptables, and figure this
thing out when pgpool and postgres configuration / testing / tuning
etc.. is done .
As an other note I was looking into using pacemaker and all the
cluster utilities that comes with CentOS yesterday, I wonder if anyone
have any experience in using pacemaker + pgpool VS. simply using
pgpool + watchdog and delegate ip .
My first impression of pacemaker is that it seem pretty robust + mabye
I should consider proper fencing of failed nodes . On the other side
going down that route my setup becomes a whole lot more complex so I'm
not sure yet which is better for my setup which most probably will
consist of 2 nodes ( I'd have to disable cuorum and stuff ) .
I will probably look into both solutions and try figure out what works
best for us .
Any input on this is much appreciated .
AKA: CosmicB @Freenode
On 8 May 2014 07:37, Yugo Nagata <nagata at sraoss.co.jp> wrote:
> On Tue, 6 May 2014 10:54:08 +0200
> Joar Jegleim <joar.jegleim at gmail.com> wrote:
>> Hi list !
>> So I'm closing in on my 2 node postgres streaming replication setup.
>> I've advanced to my 'next step' where I now have 1 pgpool running on
>> each of the 2 postgresql servers.
>> I'm using watchdog and pgpool's heartbeat .
>> When I stop pgpool from pgpool admin gui, the other pgpool instance
>> take over and bring up the delegate ip .
>> But if I simply pull the power cable from the master server the other
>> server doesn't take over, it never promotes itself to 'master pgpool
>> instance' and doesn't bring up the delegate ip.
>> The 'non active' pgpool node then doesn't promote the slave postgres
>> to master either.
>> Is the pgpool 3.3 setup with watchdog and delegate ip supposed to
>> handle such situations, or do I have to setup some other services to
>> handle automatic failover when primary node dies ?
> This is odd. Could you please show me pgpool.conf and log messages?
>> Joar Jegleim
>> Homepage: http://cosmicb.no
>> Linkedin: http://no.linkedin.com/in/joarjegleim
>> fb: http://www.facebook.com/joar.jegleim
>> AKA: CosmicB @Freenode
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
> Yugo Nagata <nagata at sraoss.co.jp>
More information about the pgpool-general