-
Notifications
You must be signed in to change notification settings - Fork 720
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
Comments
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 <ti-community-prow-bot@tidb.io>
This was referenced Jun 20, 2023
6 tasks
4 tasks
it needs to cherry pick release-6.5 again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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: