<div dir="ltr">Hello Tatsuo,<div><br></div><div>Yes, the failover_on_backend_error is turned <b>off</b>.</div><div><img src="cid:ii_m50y9rsm0" alt="image.png" width="397" height="77"><br></div><div><br></div><div>And the pgpool config and docker manifest file is mentioned below:</div><div><br></div><div><b>pgpool.conf:</b><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">connection_cache = 'off'<br>max_pool = '1'<br>num_init_children = '380'</blockquote><div><b>** </b>Rest all parameters are using default values.</div><div> </div><div><br></div><div><b>docker manifest file for pgpool:</b><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">version: '3.8'<br><br>networks:<br> tiot-service-bridge:<br> external: true<br><br>configs:<br> pgpool_config:<br> file: /services/timescaledb-pgpool/myconf.conf<br><br>services:<br> ts-pgpool:<br> hostname: ts-pgpool<br> image: /bitnami/pgpool:4.2.5<br> networks:<br> - tsdb-service-bridge<br> ports:<br> - 6435:5432<br> configs:<br> - source: pgpool_config<br> target: /config/myconf.conf<br> uid: '1001'<br> gid: '0'<br> mode: 0644<br> environment:<br> - PGPOOL_USER_CONF_FILE=/config/myconf.conf<br> - PGPOOL_BACKEND_NODES=0:db-node-1:5432,1:db-node-2:5432,2:db-node-3:5432<br> - PGPOOL_POSTGRES_USERNAME=postgres<br> - PGPOOL_POSTGRES_PASSWORD=Passw0rd<br> - PGPOOL_SR_CHECK_USER=repmgr<br> - PGPOOL_SR_CHECK_PASSWORD=Passw0rd<br> - PGPOOL_ENABLE_LDAP=no<br> - PGPOOL_ENABLE_LOAD_BALANCING=no<br> - PGPOOL_ADMIN_USERNAME=postgres<br> - PGPOOL_ADMIN_PASSWORD=Passw0rd<br> - PGPOOL_POSTGRES_CUSTOM_USERS=app_user,tsdb<br> - PGPOOL_POSTGRES_CUSTOM_PASSWORDS=Passw0rd,Passw0rd<br> - PGPOOL_CHILD_LIFE_TIME=300<br> deploy:<br> resources:<br> reservations:<br> cpus: '1'<br> memory: 512M<br> restart_policy:<br> condition: any<br> sysctls:<br> - net.ipv4.tcp_keepalive_time=600<br> - net.ipv4.tcp_keepalive_intvl=30<br> - net.ipv4.tcp_keepalive_probes=10<br> healthcheck:<br> test: ["CMD", "/opt/bitnami/scripts/pgpool/healthcheck.sh"]<br> interval: 1m<br> timeout: 20s<br> retries: 5<br> start_period: 30s<br></blockquote><div><br></div><div> </div></div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, 23 Dec 2024 at 07:56, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Hello,<br>
> <br>
> Along with other services running in docker swarm architecture I have a<br>
> database server of 3 PostgreSQL nodes deployed in Patroni + ETCD HA<br>
> Solution and a connection pooling method, PgPool-II.<br>
> <br>
> PostgreSQL Version: 13.8<br>
> PgPool Version: 4.2.5<br>
> HA Cluster-Management of Database: Patroni + ETCD (1 Primary + 2 Standby)<br>
> <br>
> ** Note: Load Balancing is disabled. All the read-write operations are<br>
> routed only to Primary Node.<br>
> <br>
> *Issue:* Frequent logs related to failover or failback event detected.<br>
> Pgpool-II Logs:<br>
> <br>
>> 2024-12-19 18:09:45: pid 776: LOG: failover or failback event detected<br>
>> 2024-12-19 18:09:45: pid 776: DETAIL: restarting myself<br>
> <br>
> <br>
> I also tracked the database logs, but didn't find any logs relevant to the<br>
> issue.<br>
> Database Logs:<br>
> <br>
>> 2024-12-19 18:09:45 UTC [81078]: [67646169.13cb6-1]<br>
>> [unknown]@[unknown],app=[unknown] [00000] LOG: connection received:<br>
>> host=10.10.1.122 port=42172<br>
>> 2024-12-19 18:09:45 UTC [81078]: [67646169.13cb6-2] tsdb@tsdb,app=[unknown]<br>
>> [00000] LOG: connection authorized: user=tsdb database=tsdb<br>
> <br>
> <br>
> As per my understanding, these pgpool-II logs occur when Pgpool-II is not<br>
> able to communicate with PostgreSQL nodes. Which happens probably when<br>
> Database is not running or service is restarted.<br>
> But the database service seems to be running normally.<br>
<br>
Yes, but in addition to this, communication error between pgpool and<br>
PostgreSQL is treated as PostgreSQL down event too.<br>
<br>
> Please help on this issue. Am I missing something to check or there can be<br>
> any other issue?<br>
<br>
Do you turn off failover_on_backend_error?<br>
<br>
Can you share pgpool.conf? (you can make it blank sensitive<br>
information such as password and IP address).<br>
<br>
Best reagards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS K.K.<br>
English: <a href="http://www.sraoss.co.jp/index_en/" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en/</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><b><u><font color="#4c1130">Thanks & Regards</font></u></b><div>Aviral Singh</div><div>Contact No: 8765789951 </div></div></div>