| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Anjul Tyagi <anjul(at)ibosstech-us(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PgBouncer - HA Mode |
| Date: | 2020-02-17 12:04:59 |
| Message-ID: | 917c4186-611e-e4c5-c715-b5300f97f98c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 2020-02-17 11:42, Anjul Tyagi wrote:
> we are using PgBouncer for connection pooling, now all are application
> is connecting database via PgBouncer. However I need suggestion, if some
> how VM goes down or something goes wrong with PgBouncer, how can we
> handle that situation. We observe that currently its a single point of
> failure for all application if PgBouncer goes down.
>
> Is there any kind of load balancer or replicate the PgBouncer ti manage
> the high availability?
A typical approach is to run several pgbouncer instances on separate
hosts and use a TCP/IP-level load balancer (e.g., hardware load balancer
or HAProxy) to route traffic.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | soumitra bhandary | 2020-02-17 12:42:23 | Re: PgBouncer - HA Mode |
| Previous Message | Anjul Tyagi | 2020-02-17 10:42:25 | PgBouncer - HA Mode |