| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Slava Bendersky <volga629(at)skillsearch(dot)ca> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: bdr replication |
| Date: | 2016-03-31 02:57:28 |
| Message-ID: | CAMsr+YGKzaWWUfr7CDwLerDaPcYz3vsEtk0-1dMayKWUbPYyHw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 31 March 2016 at 10:43, Slava Bendersky <volga629(at)skillsearch(dot)ca> wrote:
> Hello Craig,
> The current setup is two server which run libvirt and for storage which
> run glusterfs (storage server feed two virtual servers). Right now is no
> fencing in place. Each of the nodes have one PostgreSQL vm with bdr.
>
That's a disaster waiting to happen. You can't just share storage like that
in PostgreSQL, BDR or otherwise. I'm amazed it didn't fail earlier.
Try to dump whatever data you can recover, initdb a new normal PostgreSQL
instance, restore, and set up normal replication. Look into repmgr,
pgbarman, etc. Read the manual on replication, backup and failover. Do
_not_ use shared storage.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Slava Bendersky | 2016-03-31 03:09:19 | Re: bdr replication |
| Previous Message | Slava Bendersky | 2016-03-31 02:43:54 | Re: bdr replication |