Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gaGOk-0001N5-LO for pgsql-admin@arkaria.postgresql.org; Fri, 21 Dec 2018 08:43:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gaGOj-0005wP-4d for pgsql-admin@arkaria.postgresql.org; Fri, 21 Dec 2018 08:43:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gaGOi-0005wI-T5 for pgsql-admin@lists.postgresql.org; Fri, 21 Dec 2018 08:43:08 +0000 Received: from smtp1-g21.free.fr ([2a01:e0c:1:1599::10]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gaGOg-000295-7v for pgsql-admin@lists.postgresql.org; Fri, 21 Dec 2018 08:43:08 +0000 Received: from firost (unknown [81.66.185.171]) (Authenticated sender: ioguix) by smtp1-g21.free.fr (Postfix) with ESMTPSA id 193F4B00515; Fri, 21 Dec 2018 09:42:58 +0100 (CET) Date: Fri, 21 Dec 2018 09:42:57 +0100 From: "Jehan-Guillaume (ioguix) de Rorthais" To: Prince Pathria Cc: soumitra bhandary , "pgsql-admin@lists.postgresql.org" Subject: Re: Multi master implementation Message-ID: <20181221094257.51210267@firost> In-Reply-To: References: X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, 21 Dec 2018 12:43:57 +0530 Prince Pathria wrote: > Thanks Soumitra, Postgres-XC isn't getting any updates since 2015. Don't > know where it might get fail. I've also considered Postgres-XL which is in > active development state. But ver. 10 is very new to be used for producti= on. I would not deploy Postgres-XC/XL over a WAN anyway! > Curious to know how others are implementing multi master architecture!! They are using Bucardo or BDR. Or they just don't. Before sketching a very complex multi-master architecture, bench easier and safer solution first. Put all your energy to define the simplest and effective architecture you can, and bench it. You might be surprised. > On Thu, Dec 20, 2018 at 11:40 PM soumitra bhandary < > soumitra.bhandary@hotmail.com> wrote: =20 >=20 > > Well Prince , I have never worked with multiple master to be working in > > master slave replication . As you mentioned you have configured auto > > failover is this using EFM ? If you are using EFM then it won=E2=80=99t= support > > multiple master in the cluster . I have worked with BDR where all nodes= are > > worked as Master node but as you know it has downside as well . > > > > Coming to your application operation , you can segregate all read reque= st > > to be diverted to the slave nodes , may be to one synchronous node and = all > > write operation to be diverted only in Master node. In tis manner your > > application should be able to share read and write load . Anyways that = you > > would be the best person to take a call on this depending on your > > application . > > > > For multi master replication you can go through below link if that helps > > you out subjected to the implementation and compatibility with your > > application process . If any other member in this group has any experie= nce > > with multiple master with multi slave replication (apart from BDR) > > configuration experience , please share the same . > > > > https://wiki.postgresql.org/wiki/Postgres-XC > > > > Thanks > > Soumitra > > > > > > > > > > On 20-Dec-2018, at 12:21 PM, Prince Pathria > > wrote: > > > > 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 wri= te > > 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 conta= ins > > complex queries and blobs as well which makes them heavy. App code chan= ge > > 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 < =20 > > soumitra.bhandary@hotmail.com> wrote: =20 > > =20 > >> 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 > >> 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.c= om > >> > >> =20 > > =20 --=20 Jehan-Guillaume de Rorthais Dalibo