pingcap / pingcap/tidb

usability: current error log can not easily tell whether the auto analyze is killed by out of time window

Open
#64,846 1 comment 0 reactions 0 assignees View on GitHub
component/statistics sig/planner type/enhancement
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Enhancement

Image

As you can see, the error log can only tell us that the analyze was killed by a kill signal. But you will need other logs to check whether it's killed by `max_execution_time` or `time window of the auto analyze`.

This error log will now trigger an alert in Cloud. So we may need to refine it to reduce the fake alarm.

Contributor guide

Open the contributing guide

Research direction

Start by locating the auto-analyze kill logging and the related max_execution_time and time-window handling. Done means the error log distinguishes these causes clearly enough to reduce false Cloud alerts.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.