How is single-worker recycling supposed to work after max_tasks_per_child is reached?

[aysanorhun]

I am trying to understand the intended worker recycle/restart model. From reading the worker, receiver, and process manager code, this is how it looks to me:

• when max_tasks_per_child is reached, the worker stops prefetching, waits for running tasks to finish, and goes through shutdown, but the process itself does not exit
• the process manager restarts a worker either through a reload action, or when it detects that a specific worker process is no longer alive

What I want to clarify is how restarting a single worker is supposed to work. As far as I can tell:

• SIGINT / SIGTERM are shutdown signals, not restart signals
• SIGHUP reloads all workers
• ReloadOneAction restarts one worker, but I do not see a supported way to trigger that for a specific worker from within worker code
• if a worker process exits, the process manager detects it and respawns that specific worker

Right now, the only way I was able to make a specific worker get recycled was to add os._exit(1) in the worker shutdown path so the process exits and the manager respawns it. So my questions are:

1. When max_tasks_per_child is reached, is the intended behavior that the worker only goes through shutdown, or that the worker process exits and the parent respawns it?
2. Is there a supported way to recycle or restart one specific worker manually, without relying on something like os._exit(1)?

My use case is that I do not want to restart all workers. I want to recycle a specific worker once max_tasks_per_child is reached.