tidb-challenge-program / bug-hunting-issue

Bug hunting issues.
3 stars 0 forks source link

P1-[4.0 bug hunting]-[Dashboard]-wrong memory usage info for TiFlash #91

Open YKG opened 4 years ago

YKG commented 4 years ago

1. What did you do?

2. What did you expect to see?

TiFlash's memory usage is correct

3. What did you see instead?

TiFlash's memory usage is incorrect

I have another cluster which deployed on Tencent Cloud, the TiFlash node on that also shows a memory usage at 96.2%, but actually the node only has a memory usage at 65%

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

root@node3:~# /tidb-deploy/tidb-4000/bin/tidb-server -V
Release Version: v4.0.0-rc.2
Edition: Community
Git Commit Hash: dfbb1ff8b0a8d55893bcea652748c40b9a9b91ad
Git Branch: heads/refs/tags/v4.0.0-rc.2
UTC Build Time: 2020-05-15 11:54:25
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false

批注 2020-05-22 142910

shuke987 commented 4 years ago

/bug P1

YKG commented 4 years ago

/pick-up-challenge

sre-bot commented 4 years ago

@YKG sorry for this accident, we will fix it ASAP. @you06 something wrong with this challenge issue, PTAL.

you06 commented 4 years ago

/pick-up-challenge

you06 commented 4 years ago

/pick-up-challenge

you06 commented 4 years ago

/pick-up-challenge

sre-bot commented 4 years ago

@you06 pick up issue success, PTAL @tidb-challenge-program/point-team

you06 commented 4 years ago

/give-up-challenge

sre-bot commented 4 years ago

@you06 give up issue success

you06 commented 4 years ago

@YKG the pick up should work now, try again please.

YKG commented 4 years ago

/pick-up-challenge

sre-bot commented 4 years ago

@YKG pick up issue success, PTAL @tidb-challenge-program/point-team

YKG commented 4 years ago

@you06 Hi, I want to work on this bug, but it seems like TiFlash is not a open sourced repo?

I did some investigation, and according to this this design doc , the root cause must be in the server_info provider in TiFlash. Since TiFlash is not open sourced, I guess I can't continue working on this issue.

leiysky commented 4 years ago

@YKG I'm working on this bug. If there is anything you can make contribution to, I'll let you know.

YKG commented 4 years ago

/give-up-challenge

sre-bot commented 4 years ago

@YKG give up issue success

leiysky commented 4 years ago

This issue has been fixed in TiFlash's latest commit.