New config to adjust timeouts between NGINX and PHP-FPM (fix PHP zombie process)
还没有人认领这个 Issue。
- 主要语言
- C
- 星标
- 40.4k
- 派生
- 8.2k
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 96
描述
Description
Hi,
I have a question that I haven't found the answer online. I made this graph to illustrate the situation. When there are many requests waiting in the backlog queue (because the workers are busy), a time desynchronization happens between NGINX and PHP-FPM.
The PHP-FPM continues getting the requests from the backlog queue even though NGINX has already answered the client with 504 response.
This is a waste of resources, as the PHP result will never reach NGINX, as NGINX has already responded to the request with 504 to the client
When this happens the new requests receives a timeout because they go to the end of the queue and are processed with delay
If there is a configuration that takes into account the time that the process spends in the backlog queue, these "zombie" processes do not even need to be processed if they have already reached the timeout limit
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先调查 PHP-FPM 的 backlog 处理方式及其与 NGINX 超时的交互,如 issue 中所述。确定所请求的配置行为是否可行,并定义应如何处理已经超过客户端超时的请求。在形成一致同意的配置设计并验证一个超时场景后,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- nginx, php
- 领域
- backend, performance
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100