Re: Patroni set up

From: Raj <rajeshkumar(dot)dba09(at)gmail(dot)com>
To: kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com>
Cc: DINESH NAIR <Dinesh_Nair(at)iitmpravartak(dot)net>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Patroni set up
Date: 2025-07-02 14:00:31
Message-ID: CAJk5Ata3SF4jhpAZcf3dbhLjaw_=27doUq+Sv_qW8jKaO5_ojw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I want to use as minimum as possible number of nodes. But want to achive
quorum, ip rerouting, and if possible read queries on dr and also backup
must be available when one site is down

On Wed, 2 Jul 2025, 19:24 Raj, <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:

> Then what's the right architecture Kaido
>
> On Wed, 2 Jul 2025, 19:22 kaido vaikla, <kaido(dot)vaikla(at)gmail(dot)com> wrote:
>
>>
>>
>> On Wed, 2 Jul 2025 at 13:19, DINESH NAIR <Dinesh_Nair(at)iitmpravartak(dot)net>
>> wrote:
>>
>>> Hi,
>>>
>>> In my opinion this 5-node set up is very elaborate and should work ,
>>> which is distributed different across different seismic zone (across
>>> Mumbai (primary DC) and Chennai (DR site)) . Probably below mentioned
>>> parameters were factored when designing the system
>>>
>>>
>>> 1. network latency between Mumbai and Chennai
>>> 2. application switch over in case of fail-over and the downtime.
>>>
>>>
>>> Thanks
>>>
>>> Dinesh Nair
>>>
>>>
>>>
>> If Mumbai (primary DC) is down then is down pg+patroni on Chennai.
>> etcd quurom is lost
>> br
>> Kaido
>>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message kaido vaikla 2025-07-02 14:01:52 Re: Patroni set up
Previous Message Raj 2025-07-02 13:54:06 Re: Patroni set up