-
Notifications
You must be signed in to change notification settings - Fork 12
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
Custom error on memory table overflow #83
Comments
Hi Ben, I ran into this exact error. I tried increasing the values in my.cnf to no avail. (I eventually made the log files so large that it ate up all the storage on my computer.) Also, |
What happens if you put And what is the content of your my.cnf?
|
Here's what I get when I show variables. It would appear that my table size is significantly smaller than yours...
Here's what's in my.cnf...
The log file size at 1G is because I freaked out after it ate up all my storage. But the bigger problem is I'm beginning to think that my whole environment is not set up quite right. I know a lot more now than I did when I was getting this set up. For example, I have 2 versions of mysql, which is problematic. And I didn't install it using brew, which is how I installed most everything else. I'm wondering if I shouldn't just scrap it all and start again. |
If you don't have the space for the logfiles, this may be a non-starter; you're going to need 10s of GB for this. But: here's the solution. Your
|
Great! I’ll try this. In the meantime, here’s the error I get on
|
Good news! I got it to |
Currently an error can be thrown that looks like this:
The error should be wrapped in text describing the problem and its solution.
It means that the mysql configuration limits on metadata are too low; the solution is to run
bookworm config msyql
, or to manually update my.cnf to recommended values. If the problem persists, we're likely talking about a bookworm with tens of millions of items of metadata or extraordinarily long fields.The text was updated successfully, but these errors were encountered: