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

Placement policy will be lost after restarting the tidb server #28058

Closed
Tracked by #18030
lcwangchao opened this issue Sep 15, 2021 · 2 comments · Fixed by #28037
Closed
Tracked by #18030

Placement policy will be lost after restarting the tidb server #28058

lcwangchao opened this issue Sep 15, 2021 · 2 comments · Fixed by #28037
Assignees
Labels
severity/moderate sig/sql-infra SIG: SQL Infra 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 primary_region="r1" regions="r1,r2" schedule="EVEN";

-- Restart the tidb server

show placement;

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

mysql> show placement;
+-----------+-----------------------------------------------------+------------------+
| Target    | Placement                                           | Scheduling_state |
+-----------+-----------------------------------------------------+------------------+
| POLICY p1 | PRIMARY_REGION="r1" REGIONS="r1,r2" SCHEDULE="EVEN" | SCHEDULED        |
+-----------+-----------------------------------------------------+------------------+
1 row in set (0.00 sec)

3. What did you see instead (Required)

mysql> show placement;
Empty set (0.00 sec)

4. What is your TiDB version? (Required)

master

@lcwangchao lcwangchao added the type/bug The issue is confirmed as a bug. label Sep 15, 2021
@lcwangchao
Copy link
Collaborator Author

I think the reason for this bug is that full load of information schema did not cover placement policies cases

@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
severity/moderate sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants