Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j3f9H-0007t0-Bt for pgsql-admin@arkaria.postgresql.org; Mon, 17 Feb 2020 12:05:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j3f9F-0001tY-N3 for pgsql-admin@arkaria.postgresql.org; Mon, 17 Feb 2020 12:05:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j3f9E-0001tR-7X for pgsql-admin@lists.postgresql.org; Mon, 17 Feb 2020 12:05:13 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j3f96-00048L-BC for pgsql-admin@postgresql.org; Mon, 17 Feb 2020 12:05:10 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 3392E5F4; Mon, 17 Feb 2020 07:05:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 17 Feb 2020 07:05:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=d5WJw6pbvIluqkHVYlKlFxCPoBDvmg9vqwCL1BP4D Sw=; b=BsQRTExxSQv5DuHFgKGl6/ciiiP6Fd9iw37au4d5VtMVhHH/UyubA3hs4 fAYexY6twBX81gWogD5x5Pwh8W/p5StjQDijAsiWr2Q3Jojyl1k9CFgthod/BpX3 o+mpXGAjB9ftXEPAtY4AaNGdNyjxOkRvmNbSrOOdUh3LDaTMQ+MyWBXbAZ9lrpuL JUufd7DFtQYJVsI5UnlPIrPJ/Zbvnj9qCVlPt6AmDg3zkO36nYrEftPlV0WiLyzn 6ILTOCkWH3MsT+yXtOQ2JKZlqRmU5ix+f7K4xJxPugkUrw7PeuSkDfaycCN71jJ1 qhnohYTgHcQF2AUeB/qdit3TShN/w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrjeeigdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhfhokffffgggjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqh hurggurhgrnhhtrdgtohhmqeenucffohhmrghinhepvdhnughquhgrughrrghnthdrtgho mhenucfkphepleefrddvgedvrddvheehrdduuddvnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhhtsedv nhguqhhurggurhgrnhhtrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p5df2ff70.dip0.t-ipconnect.de [93.242.255.112]) by mail.messagingengine.com (Postfix) with ESMTPA id AF53D328005E; Mon, 17 Feb 2020 07:05:00 -0500 (EST) Subject: Re: PgBouncer - HA Mode To: Anjul Tyagi , pgsql-admin References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <917c4186-611e-e4c5-c715-b5300f97f98c@2ndquadrant.com> Date: Mon, 17 Feb 2020 13:04:59 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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