Re: [ADMIN] How do you manage cluster replication and failover ?
От | Steven Chang |
---|---|
Тема | Re: [ADMIN] How do you manage cluster replication and failover ? |
Дата | |
Msg-id | CAEJt7k09zzKPDsenSCe0_X9K8C7uZHph2odAG8qzZNXzCR4nFQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [ADMIN] How do you manage cluster replication and failover ? (stevenchang1213 <stevenchang1213@gmail.com>) |
Список | pgsql-admin |
you are talking about product features. I suggest u study by urself. None will confirm u anything here. All is free charge here , you should think about what it means.steven-------- 原始訊息 --------自: Robin LUCBERNET <rlucbernet@maltem.com>日期: 2017/4/7 23:33 (GMT+08:00)至: Lazaro Garcia <lazaro3487@gmail.com>, pgsql-admin@postgresql.org主旨: 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 <lazaro3487@gmail.com>
Envoyé : vendredi 7 avril 2017 15:26:41
À : Robin LUCBERNET; 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] En nombre de Robin LUCBERNET
Enviado el: jueves, 6 de abril de 2017 05:18 a. m.
Para: 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
В списке pgsql-admin по дате отправления:
Следующее
От: Steven ChangДата:
Сообщение: Re: [ADMIN] pg_dump with custom format without compression