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

resource_manager: default resource group's config is reset after restart pd server #6787

Closed
glorv opened this issue Jul 12, 2023 · 3 comments · Fixed by #6788
Closed

resource_manager: default resource group's config is reset after restart pd server #6787

glorv opened this issue Jul 12, 2023 · 3 comments · Fixed by #6788
Labels
affects-7.1 This bug affects the 7.1.x(LTS) versions. severity/major type/bug The issue is confirmed as a bug.

Comments

@glorv
Copy link
Contributor

glorv commented Jul 12, 2023

Bug Report

What did you do?

Deploy a nightly pd server add execute:

Alter resource group default ru_per_sec = 1000000 background = (task_name = "br");

And then restart the pd server

What did you expect to see?

mysql> select * from information_schema.resource_groups;
+---------+------------+----------+-----------+-------------+-----------------+
| NAME    | RU_PER_SEC | PRIORITY | BURSTABLE | QUERY_LIMIT | BACKGROUND      |
+---------+------------+----------+-----------+-------------+-----------------+
| default | 1000000    | MEDIUM   | YES       | NULL        | TASK_NAMES='br' |
+---------+------------+----------+-----------+-------------+-----------------+

What did you see instead?

mysql> select * from information_schema.resource_groups;
+---------+------------+----------+-----------+-------------+------------+
| NAME    | RU_PER_SEC | PRIORITY | BURSTABLE | QUERY_LIMIT | BACKGROUND |
+---------+------------+----------+-----------+-------------+------------+
| default | UNLIMITED  | MEDIUM   | YES       | NULL        | NULL       |
+---------+------------+----------+-----------+-------------+------------+

What version of PD are you using (pd-server -V)?

@glorv glorv added the type/bug The issue is confirmed as a bug. label Jul 12, 2023
@glorv
Copy link
Contributor Author

glorv commented Jul 12, 2023

/label affects-7.1

@ti-chi-bot ti-chi-bot bot added the affects-7.1 This bug affects the 7.1.x(LTS) versions. label Jul 12, 2023
@glorv
Copy link
Contributor Author

glorv commented Jul 12, 2023

/label severity/major

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jul 12, 2023

@glorv: The label(s) severity/major cannot be applied. These labels are supported: Hacktoberfest, challenge-program, ci-unstable, compatibility-breaker, high-performance, hptc, needs-cherry-pick-release-5.2, needs-cherry-pick-release-5.3, needs-cherry-pick-release-5.4, needs-cherry-pick-release-6.0, needs-cherry-pick-release-6.1, needs-cherry-pick-release-6.2, needs-cherry-pick-release-6.3, needs-cherry-pick-release-6.4, needs-cherry-pick-release-6.5, needs-cherry-pick-release-6.6, needs-cherry-pick-release-7.0, needs-cherry-pick-release-7.1, needs-cherry-pick-release-7.2, release-note, require-LGT1, wontfix, affects-5.2, affects-5.3, affects-5.4, affects-6.0, affects-6.1, affects-6.2, affects-6.3, affects-6.4, affects-6.5, affects-6.6, affects-7.0, affects-7.1, affects-7.2, may-affects-5.2, may-affects-5.3, may-affects-5.4, may-affects-6.0, may-affects-6.1, may-affects-6.2, may-affects-6.3, may-affects-6.4, may-affects-6.5, may-affects-6.6, may-affects-7.0, may-affects-7.1, may-affects-7.2.

In response to this:

/label severity/major

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.1 This bug affects the 7.1.x(LTS) versions. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants