| From: | Slava Bendersky <volga629(at)skillsearch(dot)ca> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: bdr replication |
| Date: | 2016-03-31 02:43:54 |
| Message-ID: | 1110942959.2074299.1459392234753.JavaMail.zimbra@skillsearch.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
volga629.
From: "Craig Ringer" <craig(at)2ndquadrant(dot)com>
To: "volga629" <volga629(at)skillsearch(dot)ca>
Cc: "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, 30 March, 2016 23:20:49
Subject: Re: [GENERAL] bdr replication
On 31 March 2016 at 09:38, Slava Bendersky < volga629(at)skillsearch(dot)ca > wrote:
Hello Everyone,
I am looking for suggestion how to recover bdr replication.
The short story we have 2 virtual nodes with share storage.
Can you describe the "shared storage" setup in more detail?
In general, with PostgreSQL "shared storage" is a shortcut to "massive database corruption" unless you have extremely careful fencing and STONITH.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-03-31 02:57:28 | Re: bdr replication |
| Previous Message | Craig Ringer | 2016-03-31 02:20:49 | Re: bdr replication |