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

Create table failed with placement rule when SCHEDULE="majority_in_primary" and PRIMARY_REGION and REGIONS are the same #31271

Closed
Tracked by #18030
lcwangchao opened this issue Jan 4, 2022 · 1 comment · Fixed by #31312
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

lcwangchao commented Jan 4, 2022

The below statement should success

mysql> create table t2(a int) primary_region="r1" regions="r1" SCHEDULE='majority_in_primary';
ERROR 8243 (HY000): "[PD:placement:ErrRuleContent]invalid rule content, rule 'table_rule_132_1' from rule group 'TiDB_DDL_132' can not match any store"
@lcwangchao lcwangchao changed the title Create table failed with placement rule when SCHEDULE="majority_in_primary" and PRIMARY_REGION and REGIONS are the same Create table failed with placement rule when SCHEDULE="majority_in_primary" and PRIMARY_REGION and REGIONS are the same Jan 4, 2022
@lcwangchao lcwangchao added type/bug The issue is confirmed as a bug. feature/developing the related feature is in development severity/moderate labels Jan 4, 2022
xhebox added a commit to xhebox/tidb that referenced this issue Jan 5, 2022
@github-actions
Copy link

github-actions bot commented Jan 5, 2022

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
Development

Successfully merging a pull request may close this issue.

1 participant