Skip to content

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

@qw4990

Description

@qw4990

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects-4.0This bug affects 4.0.x versions.affects-5.4This bug affects the 5.4.x(LTS) versions.affects-6.1This bug affects the 6.1.x(LTS) versions.affects-6.5This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.epic/sql-plan-managementimpact/panicreport/customerCustomers have encountered this bug.severity/majorsig/plannerSIG: Plannertype/bugThe issue is confirmed as a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions