通过dmkit调用unit,导致出现很多CLOSE_WAIT,
- Dominant language
- C++
- Stars
- 321
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
目前现状: 两台百度云服务器 8核16G,部署了两套集群应用,两台分别部署过dmkit,
项目已经跑了一年多,基本上处于稳定状况,最近随着客户用户的增多,服务器上渐渐多了很多CLOSE_WAIT,经过排查,发现是通过dmkit调用unit这个接口没有响应,导致出现很多CLOSE_WAIT,本系统中,只有一个调用外呼接口,其他的都是操作数据库。能帮忙排查下,unit的qps是不是不够了,
unit信息如下: bootid: 14895 线上环境: 华南大区(su)
这个项目是当初是和百度unit合作的项目,应该是没有付费的,劳烦帮忙排查下。
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the dmkit call to the Unit interface and reproduce the unresponsive-call condition described in the report. Inspect how connections are handled when Unit does not respond, then verify completion by identifying the cause of the CLOSE_WAIT growth and confirming that the call no longer leaves accumulating connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100