public inbox for [email protected]
help / color / mirror / Atom feedFrom: [email protected] <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: Matthias Leisi <[email protected]>
Cc: [email protected]
Subject: Re: Advice on cluster architecture for two related, but distinct, use cases
Date: Mon, 11 Nov 2024 09:46:45 -0500
Message-ID: <CAJygYd1Q0Zf6U8OWVT2ET5E3sg0d3XPbEJaD0jF93d3___UH7A@mail.gmail.com> (raw)
In-Reply-To: <CAKAnmm+VQXYJAFczyo01JZoQcx4CVoM26xyUuVmjbbujR0u=5w@mail.gmail.com>
References: <[email protected]>
<CAKAnmm+VQXYJAFczyo01JZoQcx4CVoM26xyUuVmjbbujR0u=5w@mail.gmail.com>
CC
On Mon, Nov 11, 2024 at 09:28 Greg Sabino Mullane <[email protected]>
wrote:
> Some of those requirements are vague, but yes, Patroni should probably be
> the first approach you look at. If the second datacenter is just for
> redundancy, then a simple setup would be:
>
> DCA (data center A):
> Postgres server 1
> Postgres server 2
>
> DCB:
> Postgres server 3 (set no_failover: true)
>
> You will also need a DCS system of some sort (e.g. etcd on all three
> nodes), as well as a backup system (e.g. pgBackRest). Will also need to
> decide how automated you want things to be (for example, cross datacenter
> failover in the above would be manually done). It should definitely be able
> to handle your RPO/RTO requirements easily enough.
>
> [Patroni] However it seems relatively complex to set up and operate
>
>
> Setting things up can be a little complex, yes, but once done it just
> works, so very little operation resources are needed.
>
> We can not assume eg a load balancer.
>
>
> Possible via the application: see
> https://www.postgresql.org/docs/current/libpq-connect.html (esp.
> target_session_attrs)
>
> Cheers,
> Greg
>
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Advice on cluster architecture for two related, but distinct, use cases
In-Reply-To: <CAJygYd1Q0Zf6U8OWVT2ET5E3sg0d3XPbEJaD0jF93d3___UH7A@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox