From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Anjul Tyagi <anjul@ibosstech-us.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: PgBouncer - HA Mode
Date: Mon, 17 Feb 2020 13:04:59 +0100
Message-ID: <917c4186-611e-e4c5-c715-b5300f97f98c@2ndquadrant.com> (raw)
In-Reply-To: <eme7c3a68e-c860-4a17-97aa-6124e2ba529e@iboss01108>
References: <eme7c3a68e-c860-4a17-97aa-6124e2ba529e@iboss01108>
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
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: peter.eisentraut@2ndquadrant.com, anjul@ibosstech-us.com
Subject: Re: PgBouncer - HA Mode
In-Reply-To: <917c4186-611e-e4c5-c715-b5300f97f98c@2ndquadrant.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