From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Jody McIntyre <jodym(at)trustcentric(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping |
Date: | 2011-02-22 03:00:52 |
Message-ID: | AANLkTikD6V4zj1T8NiT8jdWT3wuaF3yRihBRzvfbPN69@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Feb 22, 2011 at 2:26 AM, Jody McIntyre <jodym(at)trustcentric(dot)com> wrote:
> Has anyone successfully configured heartbeat + pacemaker (or any other HA
> package for that matter) to control PostgreSQL in log shipping mode? All
> the examples I've found use drbd.
>
> My current thinking is to start/stop the database as in a non HA setup
> (using upstart, since this is Ubuntu), and write a custom pacemaker resource
> agent such that:
>
> - "start" on the secondary creates a trigger file and waits for recovery to
> complete before returning success. "stop" does nothing (returns success.)
> Pacemaker would be configured for manual failback.
> - "start" and "stop" on the primary does nothing. We would STONITH the
> primary before taking over the database.
>
> Does this sound reasonable?
The resource agents for MySQL and DRBD have been implemented as
master/slave ones. So I think that the resource agent for PostgreSQL also
should be done the same way, i.e., you should implement only "start" and
"stop" but also "promote" and "demote".
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | antonio galery | 2011-02-22 12:52:31 | Hight consumption of physical memory |
Previous Message | Selva manickaraja | 2011-02-22 00:55:48 | Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping |