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

P1-[4.0 bug hunting]-[Dashboard]-Missing disk info in Cluster Diagnose Report #101

Open
YKG opened this issue May 27, 2020 · 7 comments · Fixed by pingcap/tidb-dashboard#624

Comments

@YKG
Copy link

YKG commented May 27, 2020

1. What did you do?

  • deploy a cluster on Tencent Cloud with tiup cluster
  • visit dashboard -- cluster diagnose
  • start a diagnose job
  • view full report
  • check Cluster Hardware table

2. What did you expect to see?

The DISK(GB) column should be filled with the disk capacity of each host.

3. What did you see instead?

The column is empty

bug0

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

v4.0.0-rc.2

@YKG
Copy link
Author

YKG commented May 27, 2020

I didn't dig much, but this SQL is not enough because on Tencent Cloud, the device_name is vda1

bug0-1

Another thing is it seems like there is no TiKV disk info in the CLUSTER_HARDWARE table

@breezewish
Copy link

@crazycs520 PTAL

@shuke987
Copy link

shuke987 commented Jun 2, 2020

/bug P1

@YKG
Copy link
Author

YKG commented Jun 2, 2020

@shuke987 May I get another bug P1 point for

Another thing is it seems like there is no TiKV disk info in the CLUSTER_HARDWARE table

@shuke987
Copy link

shuke987 commented Jun 2, 2020

@shuke987 May I get another bug P1 point for

Another thing is it seems like there is no TiKV disk info in the CLUSTER_HARDWARE table

The bug hunting project finished at May 30th. Thank you

@YKG
Copy link
Author

YKG commented Jun 2, 2020

@shuke987 I know that, but I reported 6 days ago and you can check the comment time.

Screenshot from 2020-06-02 17-49-22

@shuke987
Copy link

shuke987 commented Jun 2, 2020

ok, you may open another issue to report this bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants