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

followers in information_schema.placement_rules is not right when do not specify followers in placement #31702

Closed
Tracked by #18030
lcwangchao opened this issue Jan 14, 2022 · 2 comments · Fixed by #31927
Labels
feature/developing the related feature is in development severity/moderate type/bug The issue is confirmed as a bug.

Comments

@lcwangchao
Copy link
Collaborator

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create placement policy p1 constraints='[+region=r1]';
select policy_name,followers from information_schema.placement_rules where policy_name='p1';

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

followers should not be 0

3. What did you see instead (Required)

mysql> select policy_name,followers from information_schema.placement_rules where policy_name='p1';
+-------------+-----------+
| policy_name | followers |
+-------------+-----------+
| p1          |         0 |
+-------------+-----------+
1 row in set (0.00 sec)

4. What is your TiDB version? (Required)

master

mysql> select tidb_version();
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version()                                                                                                                                                                                                                                                                                                                   |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v5.5.0-alpha
Edition: Community
Git Commit Hash: 706abd66aea261ed783f0771411e71d99ae1b32d
Git Branch: heads/refs/tags/v5.5.0-alpha
UTC Build Time: 2022-01-11 14:54:32
GoVersion: go1.16.4
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
@lcwangchao lcwangchao added type/bug The issue is confirmed as a bug. feature/developing the related feature is in development severity/moderate labels Jan 14, 2022
@morgo
Copy link
Contributor

morgo commented Jan 17, 2022

For potential implementers: it might be easier to wait for #31698 to merge, since there will surely be conflicts.

@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/developing the related feature is in development severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
2 participants