Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping
От | Fujii Masao |
---|---|
Тема | Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping |
Дата | |
Msg-id | AANLkTikD6V4zj1T8NiT8jdWT3wuaF3yRihBRzvfbPN69@mail.gmail.com обсуждение исходный текст |
Ответ на | Heartbeat + pacemaker configuration for PostgreSQL log shipping (Jody McIntyre <jodym@trustcentric.com>) |
Ответы |
Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping
|
Список | pgsql-admin |
On Tue, Feb 22, 2011 at 2:26 AM, Jody McIntyre <jodym@trustcentric.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
В списке pgsql-admin по дате отправления: