Hi
I have used pg_auto_failover for quite some time which provides automatic
failover with sync replication.
I did not have any issues yet and running around 30 clusters.
Regards Allan
man. 3. apr. 2023 kl. 08.33 skrev Inzamam Shafiq :
> Hi Guys,
>
> Hope you are doing well.
>
> Can someone ple
On Fri, 07 Apr 2023 21:16:04 +0900 (JST)
Tatsuo Ishii wrote:
> >> If node 1 hangs and once it is recognized as "down" by other nodes, it will
> >> not be used without manual intervention. Thus the disaster described above
> >> will not happen in pgpool.
> >
> > Ok, so I suppose **all** connect
>> If node 1 hangs and once it is recognized as "down" by other nodes, it will
>> not be used without manual intervention. Thus the disaster described above
>> will not happen in pgpool.
>
> Ok, so I suppose **all** connections, scripts, softwares, backups,
> maintenances
> and admins must go thr
> Scenario:
> S0 - Running Postgresql as primary, and also PgPool.
> S1 - Running Postgresql as secondary, and also PgPool.
> S2 - Running only PgPool. Has the VIP.
>
> There's no /need/ for Postgresql or PgPool on server 0 to shut down if
> it loses contact with S1 and S2, since they'll also not
On 4/7/23 05:46, Jehan-Guillaume de Rorthais wrote:
On Fri, 07 Apr 2023 18:04:05 +0900 (JST)
Tatsuo Ishii wrote:
And I believe that's part of what Cen was complaining about:
«
It is basically a daemon glued together with scripts for which you are
entirely responsible for. Any small mist
On Fri, 07 Apr 2023 18:04:05 +0900 (JST)
Tatsuo Ishii wrote:
> > And I believe that's part of what Cen was complaining about:
> >
> > «
> > It is basically a daemon glued together with scripts for which you are
> > entirely responsible for. Any small mistake in failover scripts and
> > c
> And I believe that's part of what Cen was complaining about:
>
> «
> It is basically a daemon glued together with scripts for which you are
> entirely responsible for. Any small mistake in failover scripts and
> cluster enters a broken state.
> »
>
> If you want to build something clea
On Fri, 07 Apr 2023 13:16:59 +0900 (JST)
Tatsuo Ishii wrote:
> >> > But, I heard PgPool is still affected by Split brain syndrome.
> >>
> >> Can you elaborate more? If more than 3 pgpool watchdog nodes (the
> >> number of nodes must be odd) are configured, a split brain can be
> >> avoided.
> I truly believe that this problem – HA – is PostgreSQL's, not 3rd
> party's. And it's a shame that Postgres itself doesn't solve this. So
> we're discussing it here.
Let's see what other subscribers on this forum say.
>> > What if pg1 is currently primary, pg0 is standby, both are healthy, but
On Thu, Apr 6, 2023 at 11:13 PM Tatsuo Ishii wrote:
> I am welcome you to
> join and continue the discussion on pgpool mailing list.
I truly believe that this problem – HA – is PostgreSQL's, not 3rd
party's. And it's a shame that Postgres itself doesn't solve this. So
we're discussing it here.
> Communication takes time – network latencies. What if during this
> communication, the situation becomes different?
We have to accept it (and do the best to mitigate any consequence of
the problem). I think there's no such a system which presuppose 0
communication latency.
> What if some of the
On Thu, Apr 6, 2023 at 9:17 PM Tatsuo Ishii wrote:
> With quorum failover is enabled, w0, w1, and w2 communicate each other
> to vote who is correct (if it cannot communicate, it regards other
> watchdog is down). In the case above w0 and w1 are majority and will
> win.
Communication takes time –
On 4/6/23 23:16, Tatsuo Ishii wrote:
But, I heard PgPool is still affected by Split brain syndrome.
Can you elaborate more? If more than 3 pgpool watchdog nodes (the
number of nodes must be odd) are configured, a split brain can be
avoided.
Split brain is a hard situation to avoid. I suppose OP
>> > But, I heard PgPool is still affected by Split brain syndrome.
>>
>> Can you elaborate more? If more than 3 pgpool watchdog nodes (the
>> number of nodes must be odd) are configured, a split brain can be
>> avoided.
>
> Split brain is a hard situation to avoid. I suppose OP is talking abou
On Wed, 05 Apr 2023 16:50:15 +0900 (JST)
Tatsuo Ishii wrote:
> > But, I heard PgPool is still affected by Split brain syndrome.
>
> Can you elaborate more? If more than 3 pgpool watchdog nodes (the
> number of nodes must be odd) are configured, a split brain can be
> avoided.
Split brain is a
_en/
Japanese:http://www.sraoss.co.jp
> Regards,
>
> Inzamam Shafiq
> Sr. DBA
>
> From: Tatsuo Ishii
> Sent: Wednesday, April 5, 2023 12:38 PM
> To: cyberd...@gmail.com
> Cc: inzamam.sha...@hotmail.com ;
> pgsql-general@lists.postgres
But, I heard PgPool is still affected by Split brain syndrome.
Regards,
Inzamam Shafiq
Sr. DBA
From: Tatsuo Ishii
Sent: Wednesday, April 5, 2023 12:38 PM
To: cyberd...@gmail.com
Cc: inzamam.sha...@hotmail.com ;
pgsql-general@lists.postgresql.org
Subject: Re
> BUT, even if there is a solution that parses queries to make a decision it
> I would not recommend anyone to use it unless all consequences are
> understood.
> Specifically, not every read-only query could be salefy sent to a replica,
> because they could be lagging behind the primary.
> Only app
Hi,
On Wed, 5 Apr 2023 at 01:01, Tatsuo Ishii wrote:
> Hi,
>
> I am not sure if Patroni provides load balancing feature.
>
It depends on understanding of load-balancing:
- If we talk about load balancing read-only traffic across multiple
replicas - it is very easy to achieve with Patroni.
- If
Hi,
> Hi Guys,
>
> Hope you are doing well.
>
> Can someone please suggest what is one (Patroni vs PGPool II) is best for
> achieving HA/Auto failover, Load balancing for DB servers.
I am not sure if Patroni provides load balancing feature.
> Along with this, can you please share the company/
Can someone please suggest what is one (Patroni vs PGPool II) is best
for achieving HA/Auto failover, Load balancing for DB servers. Along
with this, can you please share the company/client names using these
tools for large PG databases?
Having used pgpool in multiple production deployments
On Mon, 3 Apr 2023 06:33:46 +
Inzamam Shafiq wrote:
[...]
> Can someone please suggest what is one (Patroni vs PGPool II) is best for
> achieving HA/Auto failover, Load balancing for DB servers. Along with this,
> can you please share the company/client names using these tools for large PG
> d
On 4/3/23 01:33, Inzamam Shafiq wrote:
Hi Guys,
Hope you are doing well.
Can someone please suggest what is one (Patroni vs PGPool II) is best for
achieving HA/Auto failover, Load balancing for DB servers. Along with
this, can you please share the company/client names using these tools for
l
On 2023-03-28 17:27:27 +0200, Peter J. Holzer wrote:
> On 2023-03-28 17:08:38 +0200, Alexander Kukushkin wrote:
> > The second option - you can put all member names into permanent slots
> > configuration (using patronictl edit-config):
> > slots:
> > nodename1:
> > type: physical
> > nodena
On 2023-03-28 17:08:38 +0200, Alexander Kukushkin wrote:
> On Tue, 28 Mar 2023 at 16:55, Peter J. Holzer wrote:
>
>
> However, when we took down one node for about two hours for some tests
> recently (with some moderate traffic on the remaining node), the replica
> didn't catch up af
On 2023-03-28 11:07:04 -0400, Jeremy Smith wrote:
> On Tue, Mar 28, 2023 at 10:55 AM Peter J. Holzer wrote:
>
> The configuration includes `use_slots: true` and I can see a slot in
> pg_replication_slots on the leader.
>
> I was under the impression that this would be sufficient to p
Hi,
On Tue, 28 Mar 2023 at 16:55, Peter J. Holzer wrote:
>
> However, when we took down one node for about two hours for some tests
> recently (with some moderate traffic on the remaining node), the replica
> didn't catch up after being restarted and inspection of the logs showed
> that it was
On Tue, Mar 28, 2023 at 10:55 AM Peter J. Holzer wrote:
>
>
> The configuration includes `use_slots: true` and I can see a slot in
> pg_replication_slots on the leader.
>
> I was under the impression that this would be sufficient to prevent WALs
> from being deleted on the leader before they are
Alert : 19th , 20 July 2022
From: Abdul Sayeed
Sent: Thursday, July 21, 2022 12:49 AM
To: Sankar, Uma (Uma) **CTR**
Cc: pgsql-gene...@postgresql.org; Menon, Deepak (Deepak)
Subject: [External]Re: Patroni & PostgreSQL issue
[External Sender]
Hi Uma,
If i understand your scenario corr
Hi Uma,
If i understand your scenario correct, after failover, Patroni created
deleted files on old primary by replciating from New primary?
If that is correct, i would recommend to check lag between new primary and
old primary(now slave). if it is zero then we are good to perform failover.
Reg
Hi Sonam,
> On 02. Jun, 2020, at 13:36, Sonam Sharma wrote:
>
> Can someone please share steps or any link for how to do set up postgres
> replication using patroni. And also to test automatic failover.
all you need to know is here: https://github.com/zalando/patroni
Cheers,
Paul
31 matches
Mail list logo
