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.

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

Panic caused by tidb-dashboard profiling #4248

Closed
shhdgit opened this issue Oct 29, 2021 · 0 comments · Fixed by #4253
Closed

Panic caused by tidb-dashboard profiling #4248

shhdgit opened this issue Oct 29, 2021 · 0 comments · Fixed by #4253
Labels
affects-5.2 severity/major type/bug The issue is confirmed as a bug.

Comments

@shhdgit
Copy link
Contributor

shhdgit commented Oct 29, 2021

Bug Report

What did you do?

Open TiDB Dashboard, select Advanced Debugging -> Profiling Instance, select tikv instance and click Start Profiling. Then return to Profiling Instance page and start another profile again in 10s, PD will panic. Or select 2 pd instances, PD will also panic.

What did you expect to see?

PD won't panic.

What did you see instead?

PD panic and the cluster is unavailable.

What version of PD are you using (pd-server -V)?

Release Version: v5.2.2-2-g42fbbd3
Edition: Community
Git Commit Hash: 42fbbd3c08abe89e485d4c00ce68e37e9b053513
Git Branch: release-5.2
UTC Build Time:  2021-10-29 06:23:35
@shhdgit shhdgit added the type/bug The issue is confirmed as a bug. label Oct 29, 2021
shhdgit added a commit to shhdgit/pd that referenced this issue Oct 29, 2021
@HunDunDM HunDunDM linked a pull request Nov 1, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.2 severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants