Runtime info cause OOM when the cop task num is large #39413
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects the 5.4.x(LTS) versions.
affects-6.0
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.2
affects-6.3
affects-6.4
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run a sql with many cop task(more than 10000000 cop tasks), and then TiDB OOM
Profile: Heap in Use
![image](https://user-images.githubusercontent.com/14054293/204204136-efb4c488-5ac3-4cab-aa4c-b73d71856ab4.png)
![image](https://user-images.githubusercontent.com/14054293/204204178-ffc7e315-80f7-472f-ab6d-fdfbee786500.png)
and
2. What did you expect to see? (Required)
Runtime info doesn't use too many memory.
3. What did you see instead (Required)
OOM
4. What is your TiDB version? (Required)
master
The text was updated successfully, but these errors were encountered: