-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
mydumper OOMs in deterministic fashion for large database #8718
Comments
This is almost certainly an OOM error. We need to turn trace on and debug where the leak is. I was watching my resource consumption. It stood pretty steady at about 55GB and then all of a sudden spiked up over 100GB or RAM used. Here's a sample of the trace log before it died. Nothing strange. We must not be freeing memory when we should:
|
Large results sets were not being cleared from the buffer as those rows were being spooled. This PR fixes that. |
Repro:
cd transparency-in-pricing
$ dolt sql-server --config=config.yaml
In another shell run:
mydumper -h 127.0.0.1 -P 4000 -u root -p '' --protocol tcp --database transparency-in-pricing
I've run it three times and got the following errors at different positions:
All different file positions. The server is also crashed:
The text was updated successfully, but these errors were encountered: