On 09/05/2018 12:04 PM, Thomas Poty wrote:
> I want to get :
> Automatic failover (promoting a slave)
> Automatic Routing traffic to master
> Fencing in case of node failure.
Why would you want to fence a node that's already failed? -- You want to
fence off the master during the failover so it doe
I have a setup kind of like yours, one primary and two stanby, but
with streaming replication.
Here is what i use:
-> on application (Django webapp) servers:
|---> a local HAProxy as a frontend for database servers, doing the
fencing through a check on a custom daemon running on database servers
-
I want to get :
Automatic failover (promoting a slave)
Automatic Routing traffic to master
Fencing in case of node failure.
I already have 2 asynchronous slaves in hot standby mode + Replication
slot. I don't want to add a new node.
Le mer. 5 sept. 2018 à 18:39, Dmitri Maziuk a
écrit :
> On W
On Wed, 5 Sep 2018 17:45:05 +0200
Thomas Poty wrote:
> We have one master and 2 slaves so 3 nodes
So what is the "HA" that you're trying to "increase"? Are you adding a 3rd
slave? A 2nd master? A hot standby? All of the above?
--
Dmitri Maziuk
> How many nodes do you want run? Keep in mind that with only 2 nodes,
fencing off the right one is by definition an undecidable problem. That's
one of the features of the current linux HA stack that makes one want to go
BSD/CARP.
>
> And if you want to run fully distributed, you might want to look
On Wed, 5 Sep 2018 13:23:41 +0200
Thomas Poty wrote:
> At first glance, i may use for automatic failover PAF, a proxy HAproxy and
> for fencincg, i am a bit disappointed, i don't know what to do/use
How many nodes do you want run? Keep in mind that with only 2 nodes, fencing
off the right one i
> OK, so either patch PAF yourself (not recommended) or choose something
> else. Note that two other ways are working with Pacemaker:
> * the pgsql resource agent (see FAQ of PAF)
> * a shared disk architecture (no pgsql replication)
Probably, i will be interested by the solution "patroni-etcd-
On Wed, 5 Sep 2018 15:06:21 +0200
Thomas Poty wrote:
> > In fact, PAF does not support slots. So it is not a good candidate if
> > slot are a requirement.
> Effectively slots are a requirement we prefer to keep
OK, so either patch PAF yourself (not recommended) or choose something
else. Note
> In fact, PAF does not support slots. So it is not a good candidate if
slot are
> a requirement.
Effectively slots are a requirement we prefer to keep
> > a proxy HAproxy and
> > for fencincg, i am a bit disappointed, i don't know what to do/use
> Depend on your hardware or your virtualization t
On Wed, 5 Sep 2018 13:23:41 +0200
Thomas Poty wrote:
> Hi Jehan-Guillaume,
Hello,
> Thanks for your opinion.
>
> At first glance, i may use for automatic failover PAF,
In fact, PAF does not support slots. So it is not a good candidate if slot are
a requirement.
> a proxy HAproxy and
> for f
Hi Jehan-Guillaume,
Thanks for your opinion.
At first glance, i may use for automatic failover PAF, a proxy HAproxy and
for fencincg, i am a bit disappointed, i don't know what to do/use
How about you, do you have any preference about tools/solutions to use ?
now, I am aware that i will have to
Hi all,
On Tue, 4 Sep 2018 15:09:51 +
ROS Didier wrote:
> Hi
>I have made a lot of PostgreSQL High Availability tests (more
> than 20 by solution) and the two following products respond well to the need :
>
> (1)Repmgr (2ndQuadrant)
>
> (2)Pglookout (aiven)
Both so
On 09/04/2018 07:58 AM, Thomas Poty wrote:
- using an automatick failover
I found PAF
Could you advice any others solutions to explore or share your
experience?
LinuxHA or Patroni are the most common we run into.
JD--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*
[mailto:thomas.p...@gmail.com]
Envoyé : mardi 4 septembre 2018 16:59
À : pgsql-general@lists.postgresql.org
Objet : increasing HA
Hello,
I am looking after some advice about solution allowing to increase High
availability?
Here is a bit of context :
I have an Master-Slave architecture
- 1 master
- 2
Hello,
I am looking after some advice about solution allowing to increase High
availability?
Here is a bit of context :
I have an Master-Slave architecture
- 1 master
- 2 asynchronous slaves using replication slot
- backup is made with barman using replication slot
- Wal archiving is done to
15 matches
Mail list logo
