EDIT: First check, if you did not run out of disk-space, before resolving to the configuration-related resolution.
You seem to have a too low maximum size for your innodb_data_file_path
in your my.cnf
, In this example
innodb_data_file_path = ibdata1:10M:autoextend:max:512M
you cannot host more than 512MB of data in all innodb tables combined.
Maybe you should switch to an innodb-per-table scheme using innodb_file_per_table
.
Another possible reason is the partition being full - this is just what happened to me now.
You will also get the same error ERROR 1114 (HY000): The table '#sql-310a_8867d7f' is full
if you try to add an index to a table that is using the storage engine MEMORY.
You need to modify the limit cap set in my.cnf for the INNO_DB tables. This memory limit is not set for individual tables, it is set for all the tables combined.
If you want the memory to autoextend to 512MB
innodb_data_file_path = ibdata1:10M:autoextend:max:512M
If you don't know the limit or don't want to put a limit cap, you can modify it like this
innodb_data_file_path = ibdata1:10M:autoextend
DOCKER USERS: This also happens when you have hit around 90% of your Docker image size limit (seems like 10% is needed for caching or so). The wording is confusing, as this simply means the amount of disk space Docker can use for basically everything.
To fix, go to your Docker desktop settings > Disk > move slider a bit more to the right > Apply.
This error also appears if the partition on which tmpdir
resides fills up (due to an alter table or other
In my case, this was because the partition hosting the ibdata1 file was full.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With