-
Notifications
You must be signed in to change notification settings - Fork 728
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
Placement rule in SQL isn't compatible with rule checker when using location labels #6637
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.2
severity/major
type/bug
The issue is confirmed as a bug.
Comments
ti-chi-bot bot
pushed a commit
that referenced
this issue
Jun 20, 2023
…e checker (#6633) close #6637 Signed-off-by: Ryan Leung <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jun 20, 2023
close tikv#6637 Signed-off-by: ti-chi-bot <[email protected]>
This was referenced Jun 20, 2023
rleungx
added a commit
to rleungx/pd
that referenced
this issue
Jun 20, 2023
…e checker (tikv#6633) close tikv#6637 Signed-off-by: Ryan Leung <[email protected]>
rleungx
added a commit
to rleungx/pd
that referenced
this issue
Jun 20, 2023
…e checker (tikv#6633) close tikv#6637 Signed-off-by: Ryan Leung <[email protected]>
rleungx
added a commit
that referenced
this issue
Jun 20, 2023
#6648) * schedule: fix location label in placement rule not work well with rule checker (#6633) close #6637 Signed-off-by: Ryan Leung <[email protected]>
rleungx
added a commit
to rleungx/pd
that referenced
this issue
Jun 21, 2023
…e checker (tikv#6633) close tikv#6637 Signed-off-by: Ryan Leung <[email protected]>
6 tasks
4 tasks
it needs to cherry pick release-6.5 again |
ti-chi-bot bot
added a commit
that referenced
this issue
Dec 19, 2023
…e checker (#6660) (#6956) close #6637 Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: Ryan Leung <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.2
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
What did you do?
Consider we have a cluster (three zones, each zone has a host, and each host has multiple instances)
zone1 --- host1 --- ap --- (kv1, kv2)
zone2 --- host2 --- ap --- (kv3, kv4)
zone3 --- host3 --- tp --- (kv5, kv6)
If we create the following placement policy:
What did you expect to see?
The region peer won't be distributed in the same host.
What did you see instead?
There will be three rules in PD, and each of them has a location label setting. However, each rule's count is 1, and the location label only takes effect in one rule.
So, we still can find two replicas of a region in a host.
What version of PD are you using (
pd-server -V
)?master
The text was updated successfully, but these errors were encountered: