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 1hYjjU-00031a-RN for pgadmin-support@arkaria.postgresql.org; Thu, 06 Jun 2019 04:10:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hYjjR-0003Fq-Ax for pgadmin-support@arkaria.postgresql.org; Thu, 06 Jun 2019 04:10:29 +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 1hYjjQ-0002u6-9q for pgadmin-support@lists.postgresql.org; Thu, 06 Jun 2019 04:10:29 +0000 Received: from mail-oln040092255054.outbound.protection.outlook.com ([40.92.255.54] helo=APC01-HK2-obe.outbound.protection.outlook.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYjjL-0008OW-5O for pgadmin-support@lists.postgresql.org; Thu, 06 Jun 2019 04:10:25 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4i1++Ett4/qy89d9AlEHoHSvVDhABIeJEWLcBZZs9nU=; b=bSPNrzd/ngrEwaGEKR/jV+BGTm9HHxKvXLUeZURjNKN6YtbLOkxzzl5SxTWnjehLWIdHk0eakqUnxJHhi8HQindSqm5ozIPY8d9WAeYgQ7zcFS9jyNQiopPTHYtWj/QlycfH1xqMHM6y1SYhGK4iHFtLSTs2yd2xGprI/Tw6dfXNHbYCvtYFtTgj3DYGQdmxNP3cN0ifib/4E0fXCp9CXxv0Be0CS1Duc9NByr0nlOcFTqnUoz0kfXl1SPzldp3p8BBJezams2ns+cV6kjxq7JElWQPEgXWQT9tvn+PYPG9vsuXDbhRaottpP4yVFYv0ngS25/MlqaEialI/wUCbcQ== Received: from PU1APC01FT049.eop-APC01.prod.protection.outlook.com (10.152.252.52) by PU1APC01HT098.eop-APC01.prod.protection.outlook.com (10.152.253.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.12; Thu, 6 Jun 2019 04:10:18 +0000 Received: from BMXPR01MB3799.INDPRD01.PROD.OUTLOOK.COM (10.152.252.59) by PU1APC01FT049.mail.protection.outlook.com (10.152.253.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.12 via Frontend Transport; Thu, 6 Jun 2019 04:10:18 +0000 Received: from BMXPR01MB3799.INDPRD01.PROD.OUTLOOK.COM ([fe80::3d7b:9c19:a818:1591]) by BMXPR01MB3799.INDPRD01.PROD.OUTLOOK.COM ([fe80::3d7b:9c19:a818:1591%5]) with mapi id 15.20.1943.023; Thu, 6 Jun 2019 04:10:18 +0000 From: soumitra bhandary To: "pgadmin-support@lists.postgresql.org" , "pgsql-admin@postgresql.org" Subject: pgpool-II is not following new master node post master fail over Thread-Topic: pgpool-II is not following new master node post master fail over Thread-Index: AQHVHB2/IPfUHg1TVkqX6AUNw4EQLQ== Date: Thu, 6 Jun 2019 04:10:18 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:A680900E5B0FE3A848CC335EA7EF582BCBD4250AB7DAF2A028F92C65B7237EE2;UpperCasedChecksum:031E164FC448464594852D5040E650CFC6A1008B75DD34AE045D3E3F1B1A75A5;SizeAsReceived:6701;Count:40 x-tmn: [f5qQGYBLwmjXvNxVj3AQ34Ew07OlYLED] x-ms-publictraffictype: Email x-incomingheadercount: 40 x-eopattributedmessage: 0 x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322404)(2017031323274)(2017031324274)(1601125500)(1603101475)(1701031045);SRVR:PU1APC01HT098; x-ms-traffictypediagnostic: PU1APC01HT098: x-microsoft-antispam-message-info: F5SP6m883yOIymzW0bR7ybdP9dmsaJq+5/KqooSzqRjfzgV0kH7s/CDnYkUJBFw2fwjq7YHAerUG7a+V7hUkjPohDfYP8ZRaZ4+IYG9OPTvSakDod4VbJqjCipRdWK9Eel2YMFYpC/OtpphBb3zaTVUJteSgJFku9KBkVDlVgcupbFe8k4wALchV+eIuZgR+ Content-Type: multipart/alternative; boundary="_000_BMXPR01MB3799A4272155ABC66F20178BE0170BMXPR01MB3799INDP_" MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 60b4832c-1950-4730-7bbc-08d6ea34e2c3 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jun 2019 04:10:18.2335 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT098 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_BMXPR01MB3799A4272155ABC66F20178BE0170BMXPR01MB3799INDP_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi , I am using repmgr to manage the auto fail over process at PostgreSQL Databa= se layer in a 3 node master - slave replication . Also using pgpool-II to manage the load balancing and application connectio= n routing. But when any master failover is happening at DB side and new master is prom= oted using repmgr pgpool-II is not connecting to new master and still tryin= g to connect old master node. Here is my pgpool-II conf file parameters . Am I missing anything ? backend_hostname0 =3D 'server1' # Host name or IP address to connect to = for backend 0 backend_port0 =3D 5432 # Port number for backend 0 backend_weight0 =3D 1 # Weight for backend 0 (only in load bal= ancing mode) backend_data_directory0 =3D '/data/pgdata/10/data' # Data directory for backend 0 backend_flag0 =3D 'ALLOW_TO_FAILOVER' # Controls various backend behavior # ALLOW_TO_FAILOVER or DISALLOW_TO_FAILO= VER backend_hostname1 =3D 'server2' backend_port1 =3D 5432 backend_weight1 =3D 10 backend_data_directory1 =3D '/data/pgdata/10/data' backend_flag1 =3D 'ALLOW_TO_FAILOVER' backend_hostname2 =3D 'server3' backend_port2 =3D 5432 backend_weight2 =3D 10 backend_data_directory2 =3D '/data/pgdata/10/data' backend_flag2 =3D 'ALLOW_TO_FAILOVER' --_000_BMXPR01MB3799A4272155ABC66F20178BE0170BMXPR01MB3799INDP_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi , 

I am using repmgr to manage the auto fail over process at PostgreSQL Databa= se layer in a 3 node master - slave replication .

Also using pgpool-II to manage the load balancing and application connectio= n routing. 

But when any master failover is happening at DB side and new master is prom= oted using repmgr pgpool-II is not connecting to new master and still tryin= g to connect old master node. 

Here is my pgpool-II conf file parameters . Am I missing anything ?
  
backend_hostname0 =3D 'server1'
                    =                # Host name or IP ad= dress to connect to for backend 0
backend_port0 =3D 5432
                    =                # Port number for ba= ckend 0
backend_weight0 =3D 1
                    =                # Weight for backend= 0 (only in load balancing mode)
backend_data_directory0 =3D '/data/pgdata/10/data'
                    =                # Data directory for= backend 0
backend_flag0 =3D 'ALLOW_TO_FAILOVER'
                    =                # Controls various b= ackend behavior
                    =                # ALLOW_TO_FAILOVER = or DISALLOW_TO_FAILOVER
backend_hostname1 =3D 'server2'
backend_port1 =3D 5432
backend_weight1 =3D 10
backend_data_directory1 =3D '/data/pgdata/10/data'
backend_flag1 =3D 'ALLOW_TO_FAILOVER'

backend_hostname2 =3D 'server3'
backend_port2 =3D 5432
backend_weight2 =3D 10
backend_data_directory2 =3D '/data/pgdata/10/data'
backend_flag2 =3D 'ALLOW_TO_FAILOVER'

--_000_BMXPR01MB3799A4272155ABC66F20178BE0170BMXPR01MB3799INDP_--