Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cpu consumed by CheckStreamTimeoutLoop is growing increasingly. #14207

Closed
SunRunAway opened this issue Dec 24, 2019 · 3 comments
Closed

Cpu consumed by CheckStreamTimeoutLoop is growing increasingly. #14207

SunRunAway opened this issue Dec 24, 2019 · 3 comments
Assignees
@SunRunAway
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/release-blocker This issue blocks a release. Please solve it ASAP. type/bug The issue is confirmed as a bug.

Comments

@SunRunAway
Copy link
Contributor

SunRunAway commented Dec 24, 2019 •
edited
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.

The CPU usage of a tidb-server with very low QPS would grow increasingly.

image

image

[sunrunaway:~/Downloads]$ cat goroutine | grep CheckStreamTimeoutLoop | wc -l
7604

  1. What did you expect to see?

  2. What did you see instead?

  3. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?

v3.0.7
@SunRunAway SunRunAway added the type/bug The issue is confirmed as a bug. label Dec 24, 2019
@SunRunAway
Copy link
Contributor Author

SunRunAway commented Dec 24, 2019 •
edited
Loading

The root cause is that recycleIdleConnArray does not stop its CheckStreamTimeoutLoop.

@SunRunAway SunRunAway self-assigned this Dec 24, 2019
@SunRunAway SunRunAway added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. difficulty/easy priority/release-blocker This issue blocks a release. Please solve it ASAP. labels Dec 24, 2019
@SunRunAway SunRunAway changed the title Cpu consumed by CheckStreamTimeoutLoop is growing. Cpu consumed by CheckStreamTimeoutLoop is growing increasingly. Dec 24, 2019
@SunRunAway
Copy link
Contributor Author

We should fix it in v3.0.8

@SunRunAway
Copy link
Contributor Author

This issue is fixed by #13812, but not cherry-picked.

@SunRunAway SunRunAway mentioned this issue Dec 25, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SunRunAway SunRunAway

Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/release-blocker This issue blocks a release. Please solve it ASAP. type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SunRunAway