Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Restore data from three replica cluster to five replica cluster, show table table_name regions not work. #477

Closed
haiying-gao opened this issue Aug 27, 2020 · 0 comments · Fixed by pingcap/tidb#19562
Assignees
Labels
severity/major type/bug Something isn't working

Comments

@haiying-gao
Copy link

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.
    when i Restore data from three replica cluster to five replica cluster, show table table_name regions command not work.

  2. What did you expect to see?

(root@192.168.3.11:4000)[sbtest]show table sbtest1 regions;
+-----------+-----------+---------+-----------+-----------------+------------------+------------+---------------+------------+----------------------+------------------+
| REGION_ID | START_KEY | END_KEY | LEADER_ID | LEADER_STORE_ID | PEERS            | SCATTERING | WRITTEN_BYTES | READ_BYTES | APPROXIMATE_SIZE(MB) | APPROXIMATE_KEYS |
+-----------+-----------+---------+-----------+-----------------+------------------+------------+---------------+------------+----------------------+------------------+
|      1045 | t_83_     | t_88_   |      1046 |               2 | 1046, 1047, 1048 |          0 |             0 |          0 |                   15 |            16122 |
+-----------+-----------+---------+-----------+-----------------+------------------+------------+---------------+------------+----------------------+------------------+
  1. What did you see instead?
(root@192.168.3.11:4000)[sbtest]show table sbtest1 regions;
ERROR 1105 (HY000): PD returned no region
(root@192.168.3.11:4000)[sbtest]
  1. What version of BR and TiDB/TiKV/PD are you using?

    v4.0.4

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity/major type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants