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

Can't drop placement policy if policyName is part of the policyName used by range #52257

Closed
jiyfhust opened this issue Mar 31, 2024 · 2 comments · Fixed by #52254
Closed

Can't drop placement policy if policyName is part of the policyName used by range #52257

jiyfhust opened this issue Mar 31, 2024 · 2 comments · Fixed by #52254

Comments

@jiyfhust
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create placement policy mypolicy followers=4;
create placement policy mypolicy2 followers=2;
alter range global placement policy mypolicy2;
drop placement policy mypolicy;

2. What did you expect to see? (Required)

drop mypolicy return success.

3. What did you see instead (Required)

mysql> create placement policy mypolicy followers=4;
Query OK, 0 rows affected (0.11 sec)

mysql> create placement policy mypolicy2 followers=2;
Query OK, 0 rows affected (0.11 sec)

mysql> alter range global placement policy mypolicy2;
Query OK, 0 rows affected (0.00 sec)

mysql> drop placement policy mypolicy;
ERROR 8241 (HY000): Placement policy 'mypolicy' is still in use

4. What is your TiDB version? (Required)

master

@kennedy8312
Copy link

alter range global placement policy mypolicy2; seems to be supported starting from v7.5.0.

@jiyfhust
Copy link
Contributor Author

jiyfhust commented Apr 3, 2024

/label affects-7.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants