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 + TiFlash]-Disk info collector in TiFlash is incorrect #17728

Closed
sre-bot opened this issue Jun 5, 2020 · 2 comments
Assignees
Labels
severity/major type/bug The issue is confirmed as a bug.

Comments

@sre-bot
Copy link
Contributor

sre-bot commented Jun 5, 2020

Bug Hunter issue tidb-challenge-program/bug-hunting-issue#103


Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do?

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

2. What did you expect to see?

  • The DISK(GB) column of TiFlash in the report should be the same with PD's since this two VMs have the same configration
  • TiFlash disk info in Cluster Hardware database table should be also the same with PD's

3. What did you see instead?

  • in the report, TiFlash disk column is empty

    bug2
  • in the Cluster Hardware database table, TiFlash has a row count 1 when total filter is applied, but PD has 3.

    批注 2020-05-27 201145

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

v4.0.0-rc.2

Additional notes

A deploy on Tencent Cloud has the same problem.

@sre-bot sre-bot added the type/bug The issue is confirmed as a bug. label Jun 5, 2020
@breezewish
Copy link
Member

I think this issue should be opened in TiDB Dashboard repo instead.

@fzhedu
Copy link
Contributor

fzhedu commented Aug 25, 2020

redirect to https://github.com/pingcap-incubator/tidb-dashboard, closed it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants