From: | "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com> |
---|---|
To: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | database shutdown hang due to walsender |
Date: | 2022-06-23 10:11:55 |
Message-ID: | PH0PR11MB5191427821AF779C20C9C21CD6B59@PH0PR11MB5191.namprd11.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
Postgresql13.4 on RHEL8.4 , this server setup publication as logical replication source (an open source tool named Debezium replicate data from this Postgres database as source ), we found systemctl stop postgresql-13 hang there long time , and use pg_ctl stop
$ pg_ctl stop
waiting for server to shut down............................................................... failed
pg_ctl: server does not shut down
manually kill walsender , try gain pg_ctl stop it soon got stopped.
postgres 3291450 3287667 84 08:45 ? 00:05:42 postgres: walsender splex_deny xx.xxx.xxx.xxx(32958) idle
looks like walsender blocking PG shutdown forever. From pglogs
2022-06-23 07:45:20.107 UTC::@:[179416]:[6206-1]::2022-05-16 01:34:02 UTCLOG: received fast shutdown request
2022-06-23 07:45:20.107 UTC::@:[179416]:[6207-1]::2022-05-16 01:34:02 UTCLOG: aborting any active transactions
...
2022-06-23 07:45:20.133 UTC::@:[179416]:[6209-1]::2022-05-16 01:34:02 UTCLOG: background worker "logical replication launcher" (PID 179429) exited with exit code 1
Thanks,
James
From | Date | Subject | |
---|---|---|---|
Next Message | Ninad Shah | 2022-06-24 16:23:33 | Re: database shutdown hang due to walsender |
Previous Message | Axel Rau | 2022-06-23 09:31:09 | Re: hot_standby_feedback via intermediate replica |