Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pknAF-0004CO-TI for pgsql-general@arkaria.postgresql.org; Fri, 07 Apr 2023 14:34:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pknAD-0001dP-Hs for pgsql-general@arkaria.postgresql.org; Fri, 07 Apr 2023 14:34:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pknAD-0001cq-1Z for pgsql-general@lists.postgresql.org; Fri, 07 Apr 2023 14:34:05 +0000 Received: from mail1.dalibo.net ([51.159.93.128] helo=mail.dalibo.com) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pknA8-001SPm-Dk for pgsql-general@lists.postgresql.org; Fri, 07 Apr 2023 14:34:04 +0000 Received: from karst (larco.ioguix.net [78.202.0.6]) by mail.dalibo.com (Postfix) with ESMTPSA id 6265A1FAB3; Fri, 7 Apr 2023 16:33:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1680878023; bh=tV+y5ToUWLCVkNfmjfLloFRSBDXhOcVI5QGjwtj8jnA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=kILmGd7mvN+IxM1A3cIihf6shR6jaI0XeJ1flBSeqKDyi6jpY0kzB5vMvhG0+i3Kp 4UxByumnIM9CWWbNEdbywdW4I30y9wLm5OORyNiEBAT16X0nwwi0lXP+VXsSF6n/sv 9UFvMBmZwmuJ6GPwT4x9L6GVXDamMDyLREWRcUqE= Date: Fri, 7 Apr 2023 16:33:42 +0200 From: Jehan-Guillaume de Rorthais To: Tatsuo Ishii Cc: inzamam.shafiq@hotmail.com, cyberdemn@gmail.com, pgsql-general@lists.postgresql.org Subject: Re: Patroni vs pgpool II Message-ID: <20230407163342.28dfb304@karst> In-Reply-To: <20230407.211604.225353179882549731.t-ishii@sranhm.sra.co.jp> References: <20230407094557.3def3121@karst> <20230407.180405.1284467321161872462.t-ishii@sranhm.sra.co.jp> <20230407124612.7a6d7231@karst> <20230407.211604.225353179882549731.t-ishii@sranhm.sra.co.jp> Organization: Dalibo MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 a= bove > >> will not happen in pgpool. =20 > >=20 > > Ok, so I suppose **all** connections, scripts, softwares, backups, > > maintenances and admins must go through Pgpool to be sure to hit the > > correct primary. > >=20 > > This might be acceptable in some situation, but I wouldn't call that an > > anti-split-brain solution. It's some kind of =C2=ABsoftware hiding the = rogue node > > behind a curtain and pretend it doesn't exist anymore=C2=BB =20 >=20 > You can call Pgpool-II whatever you like. I didn't mean to be rude here. Please, accept my apologies if my words offe= nded you. I consider "proxy-based" fencing architecture fragile because you just don't know what is happening on your rogue node as long as a meatware is coming a= long to deal with it. Moreover, you must trust your scripts, configurations, procedures, admins, applications, users, replication, network, Pgpool, etc = to not fail on you in the meantime... In the Pacemaker world, where everything MUST be **predictable**, the only = way to predict the state of a rogue node is to fence it from the cluster. Eithe= r cut it from the network, shut it down or set up the watchdog so it reset itself= if needed. At the end, you know your old primary is off or idle or screaming in the void with no one to hear it. It can't harm your other nodes, data or ap= ps anymore, no matter what. > Important thing for me (and probably for users) is, if it can solve user's > problem or not. In my humble (and biased) opinion, Patroni, PAF or shared storage cluster a= re solving user's problem in regard with HA. All with PROs and CONs. All rely = on strong, safe, well known and well developed clustering concepts. Some consider they are complex pieces of software to deploy and maintain, b= ut this is because HA is complex. No miracle here. Solutions like Pgpool or Repmgr are trying hard to re-implement HA concepts but left most of this complexity and safety to the user discretion. Unfortunately, this is not the role of the user to deal with such things. T= his kind of architecture probably answer a need, a gray zone, where it is good enough. I've seen similar approach in the past with pgbouncer + bash script= ing calling themselves "fencing" solution [1]. I'm fine with it as far as people are clear about the limitations. Kind regards, [1] eg. https://www.postgresql.eu/events/pgconfeu2016/sessions/session/1348-ha-with= -repmgr-barman-and-pgbouncer/