Re: Multi master implementation

Hi Soumitra,

Sorry, please consider it as another site instead of DR.

Or if I want multiple masters in main site only i.e. [2masters+3slaves].
How should I implement that?

Our devs are planning to push applications that might have a lot of write
operations. If I say read to write ratio, [65% reads]:[35% writes]. I do
have automatic failover configured[in single master arch] but don't want
that postgres crashes due to unable to handle writes since writes contains
complex queries and blobs as well which makes them heavy. App code change
isn't an option for me.

Need your suggestions please!

Happy to help :)
Prince Pathria Systems Architect Intern Evive +91 9478670472 goevive.com

On Thu, Dec 20, 2018 at 7:30 AM soumitra bhandary <
soumitra(dot)bhandary(at)hotmail(dot)com> wrote:

> Hi Prince,
>
> BDR is something which is not that much robust as conventional master
> slave replication.
>
> Why do you want master node in DR set up ?
> Do you want to enable simultaneous write operations at DR site as well??
> Normally DR setups remain in cascade replication from one of the stand by
> node at production side .
>
> Sent from my iPhone
>
> On 19-Dec-2018, at 11:55 PM, Prince Pathria <prince(dot)pathria(at)goevive(dot)com>
> wrote:
>
> Hi,
>
> I want to how people are implementing multi master architecture in
> Postgres. For now, I've come across BDR3 and bucardo for multimaster
> approach.
>
> Though both doesn't seem to be much promising to me.
>
> Goal: 2 master and their 3 slaves. [1 master + 2 slaves] in production
> site and [1 master + 1 slave]
> in DR site.
>
> Can you guys share how you did it and what issues did you faced?
>
> Thanks in advance!
>
> Happy to help :)
> Prince Pathria Systems Architect Intern Evive +91 9478670472 goevive.com
>
>