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

Panic during initializing ResourceGroupController #7360

Closed
JmPotato opened this issue Nov 13, 2023 · 1 comment · Fixed by #7361
Closed

Panic during initializing ResourceGroupController #7360

JmPotato opened this issue Nov 13, 2023 · 1 comment · Fixed by #7361
Labels
affects-7.5 This bug affects the 7.5.x(LTS) versions. component/client Client logic. component/resource-control severity/minor type/bug The issue is confirmed as a bug.

Comments

@JmPotato
Copy link
Member

Bug Report

After updating the PD client version of TiDB, this panic occurs:

image

https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb%2Fghpr_unit_test/detail/ghpr_unit_test/37306/pipeline

Might be related to #7042.

@JmPotato
Copy link
Member Author

Root cause: we may have a mock PD client as the config provider which will give a nil response:

https://github.com/tikv/client-go/blob/9caddec1314fc756f843d7b6046038d97612f7a9/internal/mockstore/mocktikv/pd.go#L395-L397

ti-chi-bot bot pushed a commit that referenced this issue Nov 13, 2023
close #7360

Prevent `loadServerConfig` from panic.

Signed-off-by: JmPotato <ghzpotato@gmail.com>
@nolouch nolouch added the affects-7.5 This bug affects the 7.5.x(LTS) versions. label Nov 16, 2023
nolouch pushed a commit to ti-chi-bot/pd that referenced this issue Nov 16, 2023
close tikv#7360

Prevent `loadServerConfig` from panic.

Signed-off-by: JmPotato <ghzpotato@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.5 This bug affects the 7.5.x(LTS) versions. component/client Client logic. component/resource-control severity/minor type/bug The issue is confirmed as a bug.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants