Analyze Full Sampling Causes Write Blockage

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: analyze全采样导致写入阻塞

| username: lindoubled

Version: 5.3.0

image
image907×769 91.7 KB

Is the analyze_full_sampling in the image for a single table or for all tables?
After analyze_full_sampling occurred, it caused a complete write block.

2
| username: 小王同学Plus | Original post link

For all tables. This takes effect when tidb_analyze_version = 2, and it is the request sent to TiKV when analyze v2 collects statistics. You can check the status of TiKV at that time.

3
| username: cs58_dba | Original post link

In this situation, you can only stop business execution.

4
| username: tidb狂热爱好者 | Original post link

Insufficient machine performance

5
| username: tidb狂热爱好者 | Original post link

You can give it a try. In fact, a full table scan can be scheduled. You can set it to run at night.

6
| username: tidb狂热爱好者 | Original post link

Lesson 16 of this course: Statistics Management (Author: Wang Tianyi) covers this topic.

7
| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.