From: Lazaro Garcia <lazaro3487@gmail.com>
To: 'Robin LUCBERNET' <rlucbernet@maltem.com>
To: pgsql-admin@postgresql.org
Subject: Re: How do you manage cluster replication and failover ?
Date: Fri, 7 Apr 2017 12:01:15 -0400
Message-ID: <002101d2afb8$31f579a0$95e06ce0$@gmail.com> (raw)
In-Reply-To: <VI1PR0501MB2781244701D6C7317A017F03AB0C0@VI1PR0501MB2781.eurprd05.prod.outlook.com>
References: <AMXPR05MB216411C9A2BEE861B13C856AB0D0@AMXPR05MB216.eurprd05.prod.outlook.com>
<000e01d2afa2$98f71ca0$cae555e0$@gmail.com>
<VI1PR0501MB2781244701D6C7317A017F03AB0C0@VI1PR0501MB2781.eurprd05.prod.outlook.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
You can user pgbouncer + repmgr but pgbouncer is not a load balancer.
When repmgr performs failover you can configure the property promote_command
in repmgr.conf and build an script for updating the pgbouncer configuration
with the new master.
Repmgr + pgpool would be very usefull when you have more than 2 nodes
because pgpool does not knows how is the best candidate node for promoting
to master.
Regards.
De: Robin LUCBERNET [mailto:rlucbernet@maltem.com]
Enviado el: viernes, 7 de abril de 2017 11:34 a. m.
Para: Lazaro Garcia; pgsql-admin@postgresql.org
Asunto: RE: [ADMIN] How do you manage cluster replication and failover ?
Hey, thanks for your feedbacks.
I do not know about Patroni. I will have a look at it.
Could someone confirm me that all features of pgpool (connection pooling +
automatic failover) can be achieve using pgbouncer (connection pooling) +
repmgr (automatic failover) ? Is it not overkill to user repmgr + pgpool ?
Am I missing something ?
Robin.
_____
De : Lazaro Garcia < <mailto:lazaro3487@gmail.com> lazaro3487@gmail.com>
Envoyé : vendredi 7 avril 2017 15:26:41
À : Robin LUCBERNET; <mailto:pgsql-admin@postgresql.org>
pgsql-admin@postgresql.org
Objet : RE: [ADMIN] How do you manage cluster replication and failover ?
You can use repmgr because it performs automatic failover, promotes a master
mores closer to replica and follows other slaves to new master.
Then pgpool detects the new master promoted by repmgr.
Regards.
De: pgsql-admin-owner@postgresql.org
<mailto:pgsql-admin-owner@postgresql.org>
[mailto:pgsql-admin-owner@postgresql.org] En nombre de Robin LUCBERNET
Enviado el: jueves, 6 de abril de 2017 05:18 a. m.
Para: pgsql-admin@postgresql.org <mailto:pgsql-admin@postgresql.org>
Asunto: [ADMIN] How do you manage cluster replication and failover ?
Hello,
We are currently trying to setup a multi hosts databases cluster with goals:
* replication (no data-loss is "required", replication timing do not needs
to be instant)
* failover
* load-balancing (bonus)
We tried:
* synchronious replication (pgpool replication mode) + load-balancing
(pgpool) : very interesing as we can theorically failover on any node at any
moment. But even after several configuraation tweeks, we never succeed
getting good write performance.
* asynchronious replication (postgres 9.6 streaming replication) : good
write performance, good replication timings (< 1 second for small
transactions). We could loadbalance select requests using pgpool.
How do you manage your postgresql clusters ? Do you use pgpool ? pgbouncer ?
other ?
How do you manage to single access point ? usign pgpool ? pgbouncer ?
Do you use streaming replication ? WAL archiving ? How do you handle to
automatic failover ?
Robin
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: pgsql-admin@postgresql.org
Cc: lazaro3487@gmail.com, rlucbernet@maltem.com
Subject: Re: How do you manage cluster replication and failover ?
In-Reply-To: <002101d2afb8$31f579a0$95e06ce0$@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox