[MDEV-29192] Mariadb10.6.8 runs out of disk space Created: 2022-07-28 Updated: 2022-09-07 Resolved: 2022-09-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Rajeev | Assignee: | Daniel Black |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
I have installed Mariadb-10.6.8 on Amazon Web Service (AWS) RDS instance. The RDS instance has a disk capacity of 150GB and 16GB RAM and it hosts 3 databases of total size 13gb. This database serves a website which hardly has much DML operations and predominately read data from this database using stored procedures. These stored procs extensively use temporary tables and the query performance is well under 1 sec. On the website there would be only around 10 to 25 concurrent users most of the time and at peak time there would be 30 to 35 users. Please note the db engine for all tables are InnoDb The problem |
| Comments |
| Comment by Daniel Black [ 2022-07-29 ] |
|
This might be a duplicate of Can you examine the /var/lib/mysql/ibtmp1 size? |
| Comment by Rajeev [ 2022-07-30 ] |
|
Hi Daniel, Thank you for your reply. We are extensively using explicitly created temporary tables and as mentioned earlier never faced this issue on 10.3.8 version. Since the database is deployed on AWS RDS instance we do not have directory access (or at least I am not aware how to do it) so i am not sure what is the file size of /var/lib/mysql/ibtmp1. I checked the database sizes and also tried checking file size using the below queries SELECT table_schema, ROUND(SUM(data_length+index_length)/1024/1024/1024,2) "size in GB" FROM information_schema.tables GROUP BY 1 ORDER BY 2 DESC; – even though the AWS console shows the disk space used as around 80GB the individual database size returned by this query sums up to 11gb select * from information_schema.files; – this does not return any record. Since this issue is on our live website we also are looking to move back to an earlier db version and hence we have set up a 10.3.35 database (development instance) and have simulated website hits to this new database and will be observing whether the disk usage reduces as it does for 10.6.8 and if all good will check against 10.4.<last release> and 10.5.<last release>. |
| Comment by Daniel Black [ 2022-09-07 ] |
|
With explicit temporary tables it looks much more like |
| Comment by Daniel Black [ 2022-09-07 ] |
|
I'm going to close this for now. After 10.6.10 is in RDS, if it still occurs please reopen. |
| Comment by Daniel Black [ 2022-09-07 ] |
|
Visibility was obviously a problem, so thanks to thiru visibility of the size of the innodb temp tablespace is coming to information_schema.innodb_sys_tablespaces (details |