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

error when querying information_schema.tidb_hot_regions #13856

Closed
eurekaka opened this issue Dec 2, 2019 · 2 comments
Closed

error when querying information_schema.tidb_hot_regions #13856

eurekaka opened this issue Dec 2, 2019 · 2 comments
Assignees
Labels
severity/moderate sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@eurekaka
Copy link
Contributor

eurekaka commented Dec 2, 2019

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
mysql> select region_count from information_schema.tidb_hot_regions where table_id = 251;
ERROR 1105 (HY000): json: cannot unmarshal number 220353.78787878787 into Go struct field RegionStat.as_leader.statistics.flow_bytes of type uint64
  1. What did you expect to see?

No error.

  1. What did you see instead?

Error reported.

  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
mysql> select tidb_version();
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version()                                                                                                                                                                                                                                                                                      |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v4.0.0-alpha-1034-g3d66e9b2e
Git Commit Hash: 3d66e9b2e21ff1cb40f6c6267eb86d5748dbb989
Git Branch: HEAD
UTC Build Time: 2019-12-01 06:14:45
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@eurekaka eurekaka added the type/bug The issue is confirmed as a bug. label Dec 2, 2019
@zz-jason zz-jason added the sig/planner SIG: Planner label Mar 10, 2020
@zz-jason zz-jason added this to the v4.0.1 milestone May 28, 2020
@winoros winoros modified the milestones: v4.0.1, 5.0-rc Jun 5, 2020
@zz-jason zz-jason removed this from the v5.0-rc milestone Jun 6, 2020
@winoros
Copy link
Member

winoros commented Nov 23, 2021

This one should be fixed master. You can open if you meet again.

@winoros winoros closed this as completed Nov 23, 2021
@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

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

No branches or pull requests

3 participants