Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping
| От | Selva manickaraja |
|---|---|
| Тема | Re: Heartbeat + pacemaker configuration for PostgreSQL log shipping |
| Дата | |
| Msg-id | AANLkTi=toy2aE_J=wGqNgS2zeTQCoqE90meKpB9nA-_Y@mail.gmail.com обсуждение исходный текст |
| Ответ на | Heartbeat + pacemaker configuration for PostgreSQL log shipping (Jody McIntyre <jodym@trustcentric.com>) |
| Список | pgsql-admin |
Hi,
Your email just came in time. We are planning to build a heartbeat but have not decided on the right approach. Maybe we can work together.
Thank you.
Warmest Regards,
Selvam
Your email just came in time. We are planning to build a heartbeat but have not decided on the right approach. Maybe we can work together.
Thank you.
Warmest Regards,
Selvam
On Tue, Feb 22, 2011 at 1: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? Has anyone else tried this?
Thanks,
Jody
В списке pgsql-admin по дате отправления: