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.

Sign up for GitHub

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

Jump to bottom

improve show analyze status #32403

Closed
xuyifangreeneyes opened this issue Feb 16, 2022 · 0 comments · Fixed by #32215
Closed

improve show analyze status #32403

xuyifangreeneyes opened this issue Feb 16, 2022 · 0 comments · Fixed by #32215
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@xuyifangreeneyes
Copy link
Contributor

Enhancement

Currently, show analyze status only shows recent 20 analyze jobs on self instance. Besides, once TiDB reboots, all the previous analyze jobs will be cleared. That brings some inconvenience:

  1. users must log in the TiDB who is stats owner in order to check auto analyze jobs.
  2. If OOM happens, TiDB reboots and we cannot get any information from show analyze status when we try to find out whether OOM is caused by analyze.

We wish:

  1. show analyze status shows cluster-level analyze jobs
  2. The analyze history is persistent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

*: track cluster-level analyze jobs and make it persistent xuyifangreeneyes/tidb
1 participant
@xuyifangreeneyes