Re: Alternative to Multi-Master Replication with 2 Data centers??

Paul, I will read through Chapter 8, sounds like it'll be tremendously
helpful.

For the second piece here let me be more specific if I may.

We currently have 1 DB and 1 Web server in each DC.

The load balancer could detect 500 errors on the behalf of either DC so
if a DB server went down the LB would eliminate one DC within seconds.

The DB server in each data center would be running MM, so if one goes
down the entire DC will be down, and when it is put backonline MM logic
will look to get updated information from WAL and re-synch it self.

On 2014-03-31 11:54, Paul Jungwirth [via PostgreSQL] wrote:

>> We are load balancing 2 data centers.
>
> Chapter 8 of Scalable Internet Architectures has a good discussion of
> running master-master setups in separate data centers. I'd read that
> whole chapter for some of the challenges you'll face.
>
>> If DC1 goes down our LB is failing over to DC2.
>
> This sounds like it will bring down both databases. In general using
> the same machine for both load balancing and failover means that in
> practice you have no failover, because if one box goes down doubling
> the traffic will overwhelm the other one. If you want high
> availability you should have a separate warm standby in each
> datacenter, for four machines total. Otherwise you're just spending
> lots of time and money for the appearance of failover but not the
> reality. Or at least test it and make sure one failure won't cascade
> to the whole system.
>
> Good luck!
>
> Paul
>
> On Sat, Mar 29, 2014 at 11:35 AM, ethode <[hidden email]> wrote:
>
>> We are load balancing 2 data centers.
>>
>> Our current approach was using a software layer in our CMS to send data
>> between data centers, but write/update frequency made this approach
>> difficult and bug laden.
>>
>> Currently we're considering several options, of which Multi-master
>> replication appears to be the top option.
>>
>> BOTH data centers need to be writable, otherwise we could use Master/Slave.
>> If DC1 goes down our LB is failing over to DC2. The failure causing
>> failover could be DB related OR be web server related.
>>
>> It doesn't appear to be realistic to keep both DC's updated on inserts
>> and/or updates without using Multi-master or some other 3rd party software
>> that appear to do the same thing as Multi-master.
>>
>> Any other solutions I should be considering
>>
>>
>>
>> --
>> View this message in context: http://postgresql.1045698.n5.nabble.com/Alternative-to-Multi-Master-Replication-with-2-Data-centers-tp5797886.html [1]
>> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>>
>>
>> --
>> Sent via pgsql-general mailing list ([hidden email])
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general [2]
>
> --
> _________________________________
> Pulchritudo splendor veritatis.
>
> --
> Sent via pgsql-general mailing list ([hidden email])
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general [2]
>
> -------------------------
>
> If you reply to this email, your message will be added to the discussion below: http://postgresql.1045698.n5.nabble.com/Alternative-to-Multi-Master-Replication-with-2-Data-centers-tp5797886p5798028.html [3]
> To unsubscribe from Alternative to Multi-Master Replication with 2 Data centers??, click here [4].
> NAML [5]

Links:
------
[1]
http://postgresql.1045698.n5.nabble.com/Alternative-to-Multi-Master-Replication-with-2-Data-centers-tp5797886.html
[2] http://www.postgresql.org/mailpref/pgsql-general
[3]
http://postgresql.1045698.n5.nabble.com/Alternative-to-Multi-Master-Replication-with-2-Data-centers-tp5797886p5798028.html
[4]
http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&amp;node=5797886&amp;code=am9zaHVhQGV0aG9kZS5jb218NTc5Nzg4NnwtMTU2Mzc4MDQ1Ng==
[5]
http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&amp;id=instant_html%21nabble%3Aemail.naml&amp;base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&amp;breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Alternative-to-Multi-Master-Replication-with-2-Data-centers-tp5797886p5798031.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.