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

planner: TiDB server can't start due to loading binding panic #58016

Closed
qw4990 opened this issue Dec 5, 2024 · 0 comments · Fixed by #58017
Closed

planner: TiDB server can't start due to loading binding panic #58016

qw4990 opened this issue Dec 5, 2024 · 0 comments · Fixed by #58017
Labels
affects-4.0 This bug affects 4.0.x versions. affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. epic/sql-plan-management impact/panic report/customer Customers have encountered this bug. severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@qw4990
Copy link
Contributor

qw4990 commented Dec 5, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Insert some invalid queries that can cause the Optimizer panic;
  2. Restart the TiDB server;
Image

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

The TiDB Server can handle the panic and restart normally.

3. What did you see instead (Required)

It can't restart.

Since when starting, TiDB has to load all bindings into memory, but TiDB has no protective measure for panic, which causes TiDB to be unable to restart successfully.

4. What is your TiDB version? (Required)

Master

@qw4990 qw4990 added epic/sql-plan-management report/customer Customers have encountered this bug. severity/major type/bug The issue is confirmed as a bug. labels Dec 5, 2024
@qw4990 qw4990 added affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. and removed may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 may-affects-8.5 labels Dec 5, 2024
@ti-chi-bot ti-chi-bot bot closed this as completed in 821563f Dec 5, 2024
@jebter jebter added the sig/planner SIG: Planner label Dec 6, 2024
@ti-chi-bot ti-chi-bot bot added affects-4.0 This bug affects 4.0.x versions. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-5.4 This bug affects the 5.4.x(LTS) versions. labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.0 This bug affects 4.0.x versions. affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. epic/sql-plan-management impact/panic report/customer Customers have encountered this bug. severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants