-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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.
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
schema: fetch all results of internal sql would cause OOM #19358
Comments
Integrity check: |
Please edit this comment to complete the following informationBug
|
Please answer these questions before submitting your issue. Thanks!
|
Please edit this comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA)HandleUpdateStats load all previous stats, it would occupy too much memory so that to cause OOM. In fact, we can process the updates chunk by chunk. 2. SymptomOOM 3. All Trigger ConditionsHandleUpdateStats load all previous stats, it would occupy too much memory so that to cause OOM. In fact, we can process the updates chunk by chunk. 4. Workaround (optional)disable feedback 5. Affected versions[v4.0.0:v4.0.5] 6. Fixed versionsv4.0.6 |
Please answer these questions before submitting your issue. Thanks!
Minimal reproduce step (Required)
HandleUpdateStats load all previous stats, it would occupy too much memory so that to cause OOM. In fact, we can process the updates chunk by chunk.
What did you expect to see? (Required)
normally occupy memory
What did you see instead (Required)
OOM
What is your TiDB version? (Required)
v4.0.X, master
The text was updated successfully, but these errors were encountered: