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

analyze can't continue after TiDB is restarted #53087

Open
zeminzhou opened this issue May 7, 2024 · 2 comments
Open

analyze can't continue after TiDB is restarted #53087

zeminzhou opened this issue May 7, 2024 · 2 comments

Comments

@zeminzhou
Copy link
Contributor

zeminzhou commented May 7, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. analyze table xxx;
  2. kill tidb
  3. restart tidb
  4. select * from mysql.analyze_jobs;

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

The behavior of TiDB analyze after restart should be the same as the content in mysql.analyze_jobs.

3. What did you see instead (Required)

mysql.analyze_jobs show job's state is running, but TiDB does not continue to analyze after restart。

4. What is your TiDB version? (Required)

master

@zeminzhou zeminzhou added the type/bug This issue is a bug. label May 7, 2024
@hawkingrei
Copy link
Member

TiDB doesn't support the automatic recovery of 'analyze' failures. In generate, we just wait for the next auto analyze of this table.

@zeminzhou
Copy link
Contributor Author

TiDB doesn't support the automatic recovery of 'analyze' failures. In generate, we just wait for the next auto analyze of this table.

Yesh, TiDB doesn't need to redo analyze after restart. But the mysql.analyze_jobs showing that the analyze job is running will cause misunderstanding.

@hawkingrei hawkingrei added type/feature-request This is a feature requests on the product type/bug This issue is a bug. and removed type/bug This issue is a bug. type/feature-request This is a feature requests on the product labels May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants