-
Notifications
You must be signed in to change notification settings - Fork 726
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
Abnormal output from "get regions by state" #6560
Labels
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
severity/moderate
type/bug
The issue is confirmed as a bug.
Comments
JmPotato
added
affects-4.0
affects-5.0
affects-5.1
affects-5.2
affects-5.3
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.0
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.2
affects-6.3
affects-6.4
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-6.6
and removed
may-affects-5.2
may-affects-5.3
may-affects-5.4
may-affects-6.1
may-affects-6.5
may-affects-7.1
labels
Jul 13, 2023
ti-chi-bot bot
pushed a commit
that referenced
this issue
Jul 17, 2023
…6804) close #6560 Instead of maintaining its own region info cache, use the core cluster to fetch the region info inside `RegionStatistics` to make sure consistency. Signed-off-by: JmPotato <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jul 17, 2023
close tikv#6560 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jul 17, 2023
close tikv#6560 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jul 17, 2023
close tikv#6560 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jul 17, 2023
close tikv#6560 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jul 17, 2023
close tikv#6560 Signed-off-by: ti-chi-bot <[email protected]>
nolouch
added
affects-6.1
This bug affects the 6.1.x(LTS) versions.
and removed
affects-5.3
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.1
This bug affects the 6.1.x(LTS) versions.
labels
Jul 19, 2023
rleungx
pushed a commit
to rleungx/pd
that referenced
this issue
Dec 1, 2023
…ikv#6804) close tikv#6560 Instead of maintaining its own region info cache, use the core cluster to fetch the region info inside `RegionStatistics` to make sure consistency. Signed-off-by: JmPotato <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
severity/moderate
type/bug
The issue is confirmed as a bug.
Bug Report
What did you do?
Run
get regions by state
(pending peer) andget region by id
commands while investigating #6559.What did you expect to see?
Same region should have the same (or almost the same) info.
What did you see instead?
Inconsistent, and the output of
get regions by state
looks strange.get regions by state
's output comes from stats, whileget region by id
's output comes from "region info", the real question is probably whyget regions by state
is not up-to-date or wrongOutput of
get regions by state
and Output of
get region by id
What version of PD are you using (
pd-server -V
)?The text was updated successfully, but these errors were encountered: