After executing an INSERT statement in TiDB, the memory usage remains high and is not released.
Open
affects-8.5
contribution
severity/moderate
sig/execution
type/bug
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Bug Report
Please answer these questions before submitting your issue. Thanks!
### 1. Minimal reproduce step (Required)
When importing data using Navicat, a large number of 'INSERT INTO ... VALUES' SQL statements are executed. However, even after the import is completed, the TiDB server’s memory remains high for many hours and does not automatically release.
dashboard chart:
and tidb server flame graph
### 2. What did you expect to see? (Required)
tidb server memory release
### 3. What did you see instead (Required)
### 4. What is your TiDB version? (Required)
v8.5.1
Contributor guide
Assessment
This issue has not been assessed yet.