Restart Api worker due to memory leak

Problem:*
Worker Terminated
Expected outcome:

Pulpcore version:
3.22.2
Pulp plugins installed and their versions:
pulp-ansible 0.16.1
pulp-cli 0.18.0
pulp-deb 2.20.2
pulp-file 1.12.0
pulp-glue 0.18.0
pulp-rpm 3.19.3
pulpcore 3.22.4

Operating system - distribution and version:
Rhel 8.6
Other relevant data:

Is the cause of the worker termination affected by the gunicorn settings? As the result, the jobs which are being submitted to the api worker failed. Is there a graceful way to to restarted api worker when there is no current connection? To workaround the api memory leak issue, I am thinking to create a job to check the free memory and also access.log and restart api when there is no current connection.

Jun 16 15:16:03 pulpd1 gunicorn[60167]: [2023-06-16 15:16:03 -0400] [60167] [WARNING] Worker with pid 97832 was terminated due to signal 9
Jun 16 15:16:03 pulp1 gunicorn[103290]: [2023-06-16 15:16:03 -0400] [103290] [INFO] Booting worker with pid: 103290

/var/lib/pulp $ more gunicorn.conf.py
max_requests = 1000
max_requests_jitter = 50

Let’s keep/continue the discussion in Api server memory leak? , so everyone is on the same page and knows your results!